Triple
T11642251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darnassus |
E276685
|
entity |
| Predicate | statusAfterBattleForAzeroth |
P100147
|
FINISHED |
| Object | destroyed |
—
|
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: destroyed | Statement: [Darnassus, statusAfterBattleForAzeroth, destroyed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterBattleForAzeroth Context triple: [Darnassus, statusAfterBattleForAzeroth, destroyed]
-
A.
statusAfterBattleForLordaeron
Indicates the resulting state or condition of entities following the Battle for Lordaeron.
-
B.
statusAfterAttack
Indicates the resulting condition or state of an entity after an attack has occurred.
-
C.
statusAfterBattleOfFiveArmies
Indicates the condition or state of an entity following the events of the Battle of Five Armies.
-
D.
statusAfterSmaug
Indicates the resulting status or condition of an entity after an event or interaction involving Smaug has occurred.
-
E.
afterConquest
Indicates that one event, state, or condition occurs subsequent to and as a result of a conquest having taken place.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a260ab488190ab1c00d9850f3096 |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
| PDg | Predicate description generation | batch_69d87f30642c8190ad94fa061cde186b |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:39 p.m.