Triple
T36054491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry Potter's wand |
E1042905
|
entity |
| Predicate | connectedToSpellEvent |
P10008
|
FINISHED |
| Object | graveyard duel in Little Hangleton |
—
|
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: graveyard duel in Little Hangleton | Statement: [Harry Potter's wand, connectedToSpellEvent, graveyard duel in Little Hangleton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToSpellEvent Context triple: [Harry Potter's wand, connectedToSpellEvent, graveyard duel in Little Hangleton]
-
A.
connectedToEvent
chosen
Indicates that an entity has a direct association or linkage with a specific event.
-
B.
hasAssociatedSpell
Indicates that an entity is linked to or accompanied by a specific spell.
-
C.
accessedBySpell
Indicates that something is reached, activated, or utilized through the use of a spell.
-
D.
underSpellBy
Indicates that one entity is magically influenced, controlled, or enchanted by another entity.
-
E.
usedSpell
Indicates that one entity has cast or employed a particular spell on or in relation to another entity or context.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff9d9cb4f8819083682be3c483b599 |
completed | May 9, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69ff9c38bf9c8190bbb85b32f3ae3d2e |
completed | May 9, 2026, 8:42 p.m. |
Created at: May 3, 2026, 4:08 p.m.