Triple
T14639122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valyrian culture |
E343677
|
entity |
| Predicate | remnants |
P44035
|
FINISHED |
| Object | Targaryen family |
—
|
NE GENERATED |
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.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Targaryen family Context triple: [Valyrian culture, remnants, Targaryen family]
-
A.
House Targaryen
chosen
House Targaryen is a powerful Valyrian-descended noble family in the world of A Song of Ice and Fire and Game of Thrones, famed for its dragons, silver-haired lineage, and long rule over the Seven Kingdoms.
-
B.
House Baratheon
House Baratheon is one of the Great Houses of Westeros in the Game of Thrones universe, known for its stag sigil, stormy seat at Storm’s End, and its brief tenure as the royal house of the Seven Kingdoms.
-
C.
House Redwyne
House Redwyne is a powerful noble family from the Arbor in the Reach, famed for its vast fleets and production of the finest wines in Westeros.
-
D.
House Reed
House Reed is a minor but fiercely loyal Northern noble house of the crannogmen, known for its close alliance with House Stark and its mastery of guerrilla warfare in the swamps of the Neck.
-
E.
House Velaryon
House Velaryon is an ancient Valyrian noble house of Driftmark in Westeros, famed for its seafaring prowess, close ties to House Targaryen, and key role in the events of the Dance of the Dragons.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:26 a.m.