Triple
T13473487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elder Wand |
E318187
|
entity |
| Predicate | allegedMakerInLegend |
P107699
|
FINISHED |
| Object | Death |
—
|
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: Death | Statement: [Elder Wand, allegedMakerInLegend, Death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedMakerInLegend Context triple: [Elder Wand, allegedMakerInLegend, Death]
-
A.
allegedFounderInStory
Indicates that an entity is claimed or reported, within a particular narrative or account, to be the founder of something.
-
B.
allegedActor
Indicates that the subject is claimed or accused to be the actor responsible for a particular action or event, without confirming that the claim is true.
-
C.
builtByLegend
chosen
Indicates that something was created, constructed, or produced by a person or entity regarded as a legend.
-
D.
allegedAgentOf
Indicates that one entity is claimed or suspected, but not confirmed, to be the agent responsible for an action or event involving another entity.
-
E.
allegedImpostor
Indicates that one entity is claimed or suspected to be fraudulently posing as another entity.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf2447bc81908baf1f4b55095144 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.