Triple
T37509694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War against the Lich King |
E932184
|
entity |
| Predicate | hasFinalBattleLocation |
P81796
|
FINISHED |
| Object | Icecrown Citadel |
—
|
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: Icecrown Citadel | Statement: [War against the Lich King, hasFinalBattleLocation, Icecrown Citadel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinalBattleLocation Context triple: [War against the Lich King, hasFinalBattleLocation, Icecrown Citadel]
-
A.
hasBossLocation
Indicates that an entity’s boss is located at a particular place or position.
-
B.
climaxLocation
chosen
Indicates the place or setting where the most intense or pivotal moment of an event, narrative, or process occurs.
-
C.
hasVillainBaseLocation
Indicates that a villain’s primary base or headquarters is located at a specified place.
-
D.
timeOfFinalBattle
Indicates the specific point in time at which the final or decisive battle takes place.
-
E.
hasBossBattleArena
Indicates that an entity features or is associated with a specific arena or location where a boss battle takes place.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a005e8a2f7c819085bfc6f04b866d87 |
completed | May 10, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_6a005de82ef08190a015b385d1d3443c |
completed | May 10, 2026, 10:28 a.m. |
Created at: May 3, 2026, 4:17 p.m.