Triple
T36851849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World in Conflict |
E910694
|
entity |
| Predicate | mainProtagonistFaction |
P47185
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [World in Conflict, mainProtagonistFaction, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainProtagonistFaction Context triple: [World in Conflict, mainProtagonistFaction, United States]
-
A.
protagonistAllegiance
chosen
Indicates the group, cause, or side with which the main character is aligned or to which they show loyalty.
-
B.
gameFaction
Indicates that an entity belongs to, is aligned with, or is a member of a particular faction within a game.
-
C.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
D.
hasMajorFaction
Indicates that an entity possesses or is associated with a primary or dominant faction within a given context.
-
E.
hasProtagonistGroup
Indicates that a narrative work features a central group of characters who collectively serve as the main protagonists.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:13 p.m.