Triple
T36119450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Riddle’s wand |
E1044702
|
entity |
| Predicate | revealedPastSpellsAt |
P184949
|
FINISHED |
| Object | Little Hangleton graveyard |
—
|
NE NERFINISHED |
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: Little Hangleton graveyard | Statement: [Tom Riddle’s wand, revealedPastSpellsAt, Little Hangleton graveyard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revealedPastSpellsAt Context triple: [Tom Riddle’s wand, revealedPastSpellsAt, Little Hangleton graveyard]
-
A.
revealedPastSpellsTo
Indicates that one entity has disclosed or made known previously cast spells to another entity.
-
B.
numberOfKnownSpells
Indicates the quantity of spells that an entity is known or recorded to have learned or mastered.
-
C.
usedSpell
Indicates that one entity has cast or employed a particular spell on or in relation to another entity or context.
-
D.
accessedBySpell
Indicates that something is reached, activated, or utilized through the use of a spell.
-
E.
spells
Indicates that one entity writes or names the letters of a word or sequence in their correct order for another entity or context.
- F. None of above. chosen
Provenance (4 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b69a74a08190b31b1201278a2c57 |
completed | May 3, 2026, 8:56 p.m. |
Created at: May 3, 2026, 4:08 p.m.