Triple
T28519009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devar-Toi |
E721703
|
entity |
| Predicate | nameMeaningInFiction |
P64940
|
FINISHED |
| Object | the Devouring Tower |
—
|
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: the Devouring Tower | Statement: [Devar-Toi, nameMeaningInFiction, the Devouring Tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameMeaningInFiction Context triple: [Devar-Toi, nameMeaningInFiction, the Devouring Tower]
-
A.
heroNameMeaning
Indicates that a hero’s name has a particular meaning, interpretation, or etymological significance.
-
B.
nickNameMeaning
Indicates that a nickname is associated with a particular meaning, interpretation, or significance.
-
C.
codeNameMeaning
Indicates that one entity is the meaning, interpretation, or significance associated with another entity’s code name.
-
D.
nameLiterallyMeans
chosen
Indicates that the literal meaning or direct translation of one entity’s name is given by the other entity.
-
E.
currentNameMeaning
Indicates that the predicate expresses the meaning or significance of an entity’s current name.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64fa087648190abaf756ae4e8375c |
completed | May 2, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:19 a.m.