Triple
T16417762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Aemon Targaryen |
E398733
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of House Targaryen |
C37426
|
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: member of House Targaryen Context triple: [Prince Aemon Targaryen, instanceOf, member of House Targaryen]
-
A.
Targaryen monarch
A Targaryen monarch is a ruler from House Targaryen who claims and exercises sovereign authority—often through dragons and dynastic right—over the Iron Throne or other realms in Westeros.
-
B.
member of House Baratheon
A member of House Baratheon is an individual belonging to the noble Baratheon bloodline or its acknowledged cadet branches, bearing its stag sigil and associated rights, duties, and claims within the political and feudal structure of Westeros.
-
C.
member of House Tyrell
A member of House Tyrell is a noble individual from the wealthy and influential Tyrell family of Highgarden, sworn to the Iron Throne and renowned for their political cunning, chivalry, and association with the fertile Reach.
-
D.
member of House Greyjoy
A member of House Greyjoy is an ironborn noble or retainer sworn to the seafaring Greyjoy family of the Iron Islands, defined by a harsh maritime culture, raiding tradition, and loyalty to the Drowned God.
-
E.
Targaryen pretender
A Targaryen pretender is an individual who claims the legacy, bloodline, or right to rule of House Targaryen—often without clear or universally accepted legitimacy—in pursuit of the Iron Throne or Targaryen authority.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:09 a.m.