Triple
T14730108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westerosi |
E346047
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | people of Game of Thrones |
C31186
|
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: people of Game of Thrones Context triple: [Westerosi, instanceOf, people of Game of Thrones]
-
A.
Game of Thrones character
chosen
A Game of Thrones character is a fictional individual within the A Song of Ice and Fire universe whose personal ambitions, loyalties, and moral complexities drive and reflect the series’ intricate political and social conflicts.
-
B.
organization in Game of Thrones
An organization in Game of Thrones is a structured group of individuals united by a common purpose, hierarchy, and set of rules or traditions that influence political, military, religious, or social power within the world of Westeros and beyond.
-
C.
ironborn
Ironborn are a seafaring warrior people from the Iron Islands who follow the harsh "Old Way" of raiding and reaving, valuing strength, salt, and steel above all else.
-
D.
Lord of the Seven Kingdoms
The Lord of the Seven Kingdoms is the supreme sovereign who holds ultimate political, military, and legal authority over all the realms united under the Seven Kingdoms.
-
E.
organization in A Song of Ice and Fire
An organization in A Song of Ice and Fire is a structured group of individuals—such as noble houses, religious orders, military factions, or secret societies—united by shared goals, loyalties, and rules that influence political, social, and military dynamics in Westeros and beyond.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:29 a.m.