Triple
T38061364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eve of Destruction |
E950347
|
entity |
| Predicate | precededByQuest |
P52568
|
FINISHED |
| Object | The Worldstone Chamber |
—
|
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 Worldstone Chamber | Statement: [Eve of Destruction, precededByQuest, The Worldstone Chamber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededByQuest Context triple: [Eve of Destruction, precededByQuest, The Worldstone Chamber]
-
A.
hasPredecessorMission
chosen
Indicates that a mission occurs after and is directly preceded by another specific mission in a sequence.
-
B.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
C.
questProgression
Indicates the ordered advancement of a quest through its defined stages or milestones.
-
D.
consequenceOfQuest
Indicates that an event, state, or outcome occurs as a direct result of completing or progressing in a specific quest.
-
E.
precededByPersonaOf
Indicates that one entity’s persona or role comes immediately before another entity’s persona or role in a sequence or progression.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: May 3, 2026, 4:21 p.m.