Triple
T38589269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Frozen Throne |
E932415
|
entity |
| Predicate | firstLichKing |
P206557
|
FINISHED |
| Object | Ner’zhul |
E1035792
|
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: Ner’zhul | Statement: [The Frozen Throne, firstLichKing, Ner’zhul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLichKing Context triple: [The Frozen Throne, firstLichKing, Ner’zhul]
-
A.
laterLichKing
Indicates that one entity becomes the Lich King at a later time than another entity.
-
B.
formerWarchief
Indicates that one entity previously held the role or title of warchief over another entity but no longer does.
-
C.
lastKingBeforeStewards
Indicates that one entity is the final king who ruled immediately prior to the period when stewards assumed governing authority over the other entity.
-
D.
predecessorAsWarchief
Indicates that one entity previously held the position of warchief immediately before another entity.
-
E.
successorAsWarchief
Indicates that one entity becomes the next warchief, taking over the leadership role from another.
- F. None of above. chosen
Provenance (5 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a425186f58c8190bb4271084a1adf2b |
completed | June 29, 2026, 11:05 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c85e308819083dd67b96f457659 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:32 p.m.