Triple
T16923439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Targaryen civil war |
E410504
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Westeros history |
C35052
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: event in Westeros history Context triple: [Targaryen civil war, instanceOf, event in Westeros history]
-
A.
event in A Song of Ice and Fire
chosen
An event in A Song of Ice and Fire is a significant occurrence—such as a battle, feast, journey, or political maneuver—that alters the relationships, power dynamics, or fates of characters within the narrative’s historical and geographic context.
-
B.
event in Game of Thrones
An event in Game of Thrones is a significant occurrence or incident within the narrative world that impacts characters, plot progression, or the political and mystical landscape of Westeros and beyond.
-
C.
medieval event
A medieval event is a historically themed gathering or occurrence set in or inspired by the Middle Ages, often featuring period-appropriate customs, attire, activities, and social structures.
-
D.
event in ancient history
An event in ancient history is a significant occurrence or series of actions that took place in early human civilizations and has had a lasting impact on cultural, political, or social development.
-
E.
event in The Anarchy
An event in The Anarchy is a significant historical occurrence—such as a battle, treaty, succession crisis, or political maneuver—that shapes the course of the civil war between Stephen and Matilda in 12th-century England.
- F. None of above.
Provenance (1 batch)
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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:30 a.m.