Triple
T22012274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charms |
E543605
|
entity |
| Predicate | hasCoreSkill |
P96902
|
FINISHED |
| Object | wand movement |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: wand movement | Statement: [Charms, hasCoreSkill, wand movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreSkill Context triple: [Charms, hasCoreSkill, wand movement]
-
A.
hasSkillTree
Indicates that an entity is associated with a structured progression of skills or abilities, typically organized in a branching or hierarchical form.
-
B.
hasEponymousSkill
Indicates that an entity possesses a skill that is named after a particular person or entity.
-
C.
requiresSkill
Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
-
D.
indicatesSkill
chosen
Indicates a relationship where one entity possesses, demonstrates, or is associated with a particular skill represented by another entity.
-
E.
skillType
Indicates the specific category or kind of skill that characterizes or classifies an associated skill-related entity or action.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127a520bc8190865f525a87255fb2 |
completed | April 28, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:22 p.m.