Triple
T37873634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Violet Citadel |
E944664
|
entity |
| Predicate | locatedInGame |
P119381
|
FINISHED |
| Object | World of Warcraft: Wrath of the Lich King |
E274195
|
NE 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: World of Warcraft: Wrath of the Lich King | Statement: [The Violet Citadel, locatedInGame, World of Warcraft: Wrath of the Lich King]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInGame Context triple: [The Violet Citadel, locatedInGame, World of Warcraft: Wrath of the Lich King]
-
A.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
inGameLocationType
Indicates that an entity has a specific type or category of location within a game world (e.g., city, dungeon, region).
-
C.
seriesGameLocation
Indicates the location or venue where a game in a series takes place.
-
D.
gameLocation
Indicates the place or venue where a game or match takes place.
-
E.
notableGameLocation
chosen
Indicates that a particular place is recognized as a significant or prominent location within a game.
- F. None of above.
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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a47864334008190b4245d660ce3fbc6 |
completed | July 3, 2026, 9:52 a.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.