Triple
T38584306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyjal Summit |
E932311
|
entity |
| Predicate | secondaryEnemyFaction |
P84462
|
FINISHED |
| Object | Scourge |
—
|
NE NERFINISHED |
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: Scourge | Statement: [Hyjal Summit, secondaryEnemyFaction, Scourge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryEnemyFaction Context triple: [Hyjal Summit, secondaryEnemyFaction, Scourge]
-
A.
secondaryBelligerent
Indicates that an entity participates in a conflict as a secondary or supporting belligerent rather than as a primary combatant.
-
B.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
-
C.
secondaryOpponent
chosen
Indicates that an entity serves as an additional or backup opponent to a primary one in a given context or interaction.
-
D.
enemyOrganization
Indicates that one organization is considered an adversary or opponent of another organization, typically in a hostile or competitive context.
-
E.
primaryEnemyForces
Indicates that the related entities constitute the main opposing or hostile forces in a conflict or competitive situation.
- 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_69ffe613c03481909f3043ec8bf0bed9 |
completed | May 10, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69ffe4a73fb4819091600725a443981a |
completed | May 10, 2026, 1:51 a.m. |
Created at: May 3, 2026, 4:32 p.m.