Triple
T38586885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Stormwind |
E932364
|
entity |
| Predicate | notableMilitaryFigure |
P17957
|
FINISHED |
| Object | Anduin Lothar |
E318089
|
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: Anduin Lothar | Statement: [Kingdom of Stormwind, notableMilitaryFigure, Anduin Lothar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMilitaryFigure Context triple: [Kingdom of Stormwind, notableMilitaryFigure, Anduin Lothar]
-
A.
notableCommanderOf
chosen
Indicates that an individual is a distinguished or historically significant commander associated with leading a particular military unit, force, or organization.
-
B.
militaryLeader
Indicates that one entity serves as the commanding military leader of another entity, such as a state, organization, or armed force.
-
C.
notableHistoricalEntity
Indicates that an entity holds recognized historical significance or prominence within a historical context.
-
D.
notableCommanderNationality
Indicates that the notable commander associated with an entity has the specified nationality.
-
E.
notableCommanderAmerican
Indicates that the subject served as a notable military commander who is American.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a42158362248190aa60d7501b164af2 |
completed | June 29, 2026, 6:49 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.