Triple
T37874003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunreavers |
E944672
|
entity |
| Predicate | statusInDalaran |
P201433
|
FINISHED |
| Object | Horde-aligned faction |
—
|
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: Horde-aligned faction | Statement: [Sunreavers, statusInDalaran, Horde-aligned faction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInDalaran Context triple: [Sunreavers, statusInDalaran, Horde-aligned faction]
-
A.
statusInPylea
Indicates the role, condition, or standing an entity holds specifically within the realm or context of Pylea.
-
B.
statusInDerna
Indicates the specific condition, role, or situation an entity holds within the context of Derna.
-
C.
statusInSira
Indicates the status or standing that an entity holds within the Sira system or classification.
-
D.
statusAfterBattleForAzeroth
Indicates the condition or state of an entity following the events of the Battle for Azeroth.
-
E.
statusInDiabloII
Indicates the role, condition, or classification an entity holds within the context of the game Diablo II.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fff4530f908190afe9387f732c2b7e |
completed | May 10, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fff3c01a64819091196875b0c88607 |
completed | May 10, 2026, 2:56 a.m. |
| PDg | Predicate description generation | batch_69fff4525ce48190b1d760539e68aadc |
completed | May 10, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:19 p.m.