Triple
T13338138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Baratheon |
E317751
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Head of House Baratheon |
C32849
|
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: Head of House Baratheon Context triple: [Robert Baratheon, instanceOf, Head of House Baratheon]
-
A.
member of House Lannister
A member of House Lannister is an individual belonging to the powerful and wealthy noble family of Lannister, known for their political influence, ambition, and association with the Westerlands and Casterly Rock in the world of Westeros.
-
B.
Third Marshal of the Riddermark
The Third Marshal of the Riddermark is a high-ranking Rohirrim military commander responsible for leading one of Rohan’s primary field armies and defending a designated region of the Riddermark.
-
C.
member of the House of Stuart
A member of the House of Stuart is an individual belonging by birth or legitimate descent to the royal dynasty that ruled Scotland and later England, Great Britain, and Ireland between the late 14th and early 18th centuries.
-
D.
member of the Stewart family
A member of the Stewart family is an individual who belongs by birth, marriage, or legal relation to the familial group identified by the Stewart surname and its shared lineage, traditions, and relationships.
-
E.
High Steward of Scotland
The High Steward of Scotland was a hereditary noble office responsible for managing the royal household and estates, which evolved into the dynastic title held by the Stewart (later Stuart) family who became kings of Scotland and England.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:31 p.m.