Scene–Concept–Entity Extraction
Input is a batch of linear source texts. Output sce-scenes.yaml, sce-concepts.yaml, and
sce-entities.yaml in the user-selected directory, with progress in _sce-round1-progress.md. The
value is reuse: one scene can directly invoke a concept established elsewhere.
Principles
- Source first —
define and IPO come from the source and stay within 50 words. Leave
unsupported content empty rather than inventing it.
- Concepts are the hub — Establish concepts first, attach entities to concepts, and let scenes
invoke only established concepts and entities.
- Prefer omission — A candidate without its own IPO or decomposition is not a concept. Merge
abstractions into their parent and demote fragments to steps.
- Bound references — Keep two to six relations per concept and only the strongest relation for
a knowledge-element pair.
- Stop for confirmation between rounds. Never start round two before approval.
Round One: Skeleton
Process five to ten texts per batch and update _sce-round1-progress.md.
- Read the complete batch and record progress.
- Extract candidates with only
id + define + sources: scenes answer “how do I…”, concepts can
express an IPO, and entities answer “did I use X?”
- Deduplicate globally: merge at 80% or greater semantic overlap, normalize synonymous IDs, and
return overly fine steps to their parent. Record every
X → Y merge.
- Write the three YAML files and mark remaining fields
TODO.
- Stop and present deduplication and concept coverage for confirmation.
Round Two: Content
Use sources to return to the original text. Sequence words indicate steps; requirement and input
words indicate IPO inputs.
- Fill from the hub outward: concepts first with complete IPO or decomposition, entities in
parallel, then scenes with trigger, goal, and three to six progressive assembly stages.
- Read
references/relations.md; add entity hierarchy and concept–entity invocation relations.
- Run completeness checks and write
updated_at.
Completion requires a skeleton-only round one with a merge log; every concept has IPO or
decomposition; every entity passes “I used X” and has hierarchy depth at most three; every scene
invokes established concepts/entities in three to six stages; all references resolve; every
definition has a source and stays within 50 words; there are no isolated concepts; and every concept
has two to six relations.
| Layer |
Meaning |
Question |
Valid form |
| Concept |
Class: executable action |
Which method should I use? |
IPO preserves independent logic; decomposition records stages, sub-concepts, and why each is needed |
| Entity |
Instance: identifiable person, tool, product, or named framework |
What did I use? |
“I used X,” where X is not an action |
| Scene |
Assembly: problem plus orchestration |
How do I…? |
Trigger, goal, three to six stages, invocations, and constraints |
During round two, read references/relations.md for the direction and selection order of the eight
relation types.
1---2name: semantic-pkm-creator-23description: >-4 Extracts callable scenes, concepts, and entities from source text for personal knowledge5 management in two rounds: a deduplicated skeleton for human confirmation, then IPO, decomposition,6 assembly, and relations with concepts as the hub.7metadata:8 source: https://skillmd.com/skills/ontology-of-everything/semantic-pkm-creator-29 language: en10 translation_of: semantic-pkm-creator-cn11 openclaw:12 homepage: https://github.com/ontology-of-everything/concept-skills/tree/main/skills/en/semantic-pkm-creator13---1415# Scene–Concept–Entity Extraction1617Input is a batch of linear source texts. Output `sce-scenes.yaml`, `sce-concepts.yaml`, and18`sce-entities.yaml` in the user-selected directory, with progress in `_sce-round1-progress.md`. The19value is reuse: one scene can directly invoke a concept established elsewhere.2021## Principles22231. **Source first** — `define` and IPO come from the source and stay within 50 words. Leave24 unsupported content empty rather than inventing it.252. **Concepts are the hub** — Establish concepts first, attach entities to concepts, and let scenes26 invoke only established concepts and entities.273. **Prefer omission** — A candidate without its own IPO or decomposition is not a concept. Merge28 abstractions into their parent and demote fragments to steps.294. **Bound references** — Keep two to six relations per concept and only the strongest relation for30 a knowledge-element pair.315. **Stop for confirmation between rounds.** Never start round two before approval.3233## Round One: Skeleton3435Process five to ten texts per batch and update `_sce-round1-progress.md`.36371. Read the complete batch and record progress.382. Extract candidates with only `id + define + sources`: scenes answer “how do I…”, concepts can39 express an IPO, and entities answer “did I use X?”403. Deduplicate globally: merge at 80% or greater semantic overlap, normalize synonymous IDs, and41 return overly fine steps to their parent. Record every `X → Y` merge.424. Write the three YAML files and mark remaining fields `TODO`.435. Stop and present deduplication and concept coverage for confirmation.4445## Round Two: Content4647Use `sources` to return to the original text. Sequence words indicate steps; requirement and input48words indicate IPO inputs.49501. Fill from the hub outward: concepts first with complete IPO or decomposition, entities in51 parallel, then scenes with trigger, goal, and three to six progressive assembly stages.522. Read `references/relations.md`; add entity hierarchy and concept–entity invocation relations.533. Run completeness checks and write `updated_at`.5455Completion requires a skeleton-only round one with a merge log; every concept has IPO or56decomposition; every entity passes “I used X” and has hierarchy depth at most three; every scene57invokes established concepts/entities in three to six stages; all references resolve; every58definition has a source and stays within 50 words; there are no isolated concepts; and every concept59has two to six relations.6061| Layer | Meaning | Question | Valid form |62| ------- | ---------------------------------------------------------------- | -------------------------- | --------------------------------------------------------------------------------------------------- |63| Concept | Class: executable action | Which method should I use? | IPO preserves independent logic; decomposition records stages, sub-concepts, and why each is needed |64| Entity | Instance: identifiable person, tool, product, or named framework | What did I use? | “I used X,” where X is not an action |65| Scene | Assembly: problem plus orchestration | How do I…? | Trigger, goal, three to six stages, invocations, and constraints |6667During round two, read `references/relations.md` for the direction and selection order of the eight68relation types.