Triple
T38589592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burning Steppes |
E932422
|
entity |
| Predicate | primaryConflicts |
P5022
|
FINISHED |
| Object | Alliance vs Horde skirmishes |
—
|
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: Alliance vs Horde skirmishes | Statement: [Burning Steppes, primaryConflicts, Alliance vs Horde skirmishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryConflicts Context triple: [Burning Steppes, primaryConflicts, Alliance vs Horde skirmishes]
-
A.
mainConflict
chosen
Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
-
B.
secondaryConflict
Indicates a secondary or subordinate conflict that arises in addition to a primary or main conflict between entities.
-
C.
centralConflictIn
Indicates that one situation, issue, or opposition serves as the primary source of tension or struggle within another context, such as a story, event, or scenario.
-
D.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
E.
loreConflict
Indicates that there is an inconsistency, contradiction, or incompatibility between pieces of lore or canonical information.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.