Triple
T35280325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osha |
E1018917
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | servant of House Stark |
C32568
|
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: servant of House Stark Context triple: [Osha, instanceOf, servant of House Stark]
-
A.
member of House Stark
chosen
A member of House Stark is an individual belonging to the noble Stark family of the North, bound by honor, resilience, and loyalty to Winterfell and its ancient traditions.
-
B.
member of House Frey
A member of House Frey is an individual belonging to the large, politically ambitious, and often mistrusted noble family that controls the strategically vital Twins crossing in the Riverlands.
-
C.
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.
-
D.
Head of House Baratheon
The Head of House Baratheon is the ruling lord or lady of the Baratheon family, holding authority over its lands, vassals, and political alliances within the realm.
-
E.
member of House Clegane
A member of House Clegane is an individual belonging to the minor Westerosi noble family famed for its brutal martial prowess, fierce loyalty to the Lannisters, and the distinctive three black dogs on a yellow field sigil.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.