Triple
T14688521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The King in the North |
E344976
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | title in A Song of Ice and Fire |
C35011
|
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: title in A Song of Ice and Fire Context triple: [The King in the North, instanceOf, title in A Song of Ice and Fire]
-
A.
title in Middle-earth
A title in Middle-earth represents a formal or honorific designation that signifies a character’s rank, role, lineage, or renown within the societies and cultures of Tolkien’s legendarium.
-
B.
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.
-
C.
Lord of Storm's End
The Lord of Storm's End is the noble ruler of the storm-lashed coastal stronghold of House Baratheon, commanding its defenses, lands, and vassals in the eastern Stormlands.
-
D.
title of chivalry
A title of chivalry is an honorific rank or designation bestowed, often by a sovereign or recognized authority, to acknowledge an individual's exemplary bravery, service, or adherence to the ideals of knighthood.
-
E.
Game of Thrones character
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.
- F. None of above. chosen
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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:28 a.m.