Triple
T37830752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorgrond |
E943193
|
entity |
| Predicate | majorEnemyFaction |
P32752
|
FINISHED |
| Object | Iron Horde |
—
|
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: Iron Horde | Statement: [Gorgrond, majorEnemyFaction, Iron Horde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorEnemyFaction Context triple: [Gorgrond, majorEnemyFaction, Iron Horde]
-
A.
hasMajorFaction
Indicates that an entity possesses or is associated with a primary or dominant faction within a given context.
-
B.
finalBossFaction
Indicates that an entity serves as or belongs to the faction of the ultimate or final boss in a game or narrative.
-
C.
primaryEnemyForces
chosen
Indicates that the related entities constitute the main opposing or hostile forces in a conflict or competitive situation.
-
D.
enemyOrganization
Indicates that one organization is considered an adversary or opponent of another organization, typically in a hostile or competitive context.
-
E.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a002103c93081908398fa5726f5fa6e |
completed | May 10, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_6a001fcb9fb48190a27d8f2ca983fbe6 |
completed | May 10, 2026, 6:03 a.m. |
Created at: May 3, 2026, 4:19 p.m.