Triple
T35357708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Reed |
E1021382
|
entity |
| Predicate | liegeHouse |
P115966
|
FINISHED |
| Object | House Stark |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: House Stark | Statement: [House Reed, liegeHouse, House Stark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liegeHouse Context triple: [House Reed, liegeHouse, House Stark]
-
A.
seatOfLiege
Indicates that a location serves as the primary seat or base of authority for a particular liege or ruling lord.
-
B.
liegeTo
chosen
Indicates a feudal or hierarchical relationship in which one party owes allegiance, service, or loyalty to another as their superior or lord.
-
C.
vassalHouse
Indicates a feudal or subordinate relationship in which one house is bound in loyalty, service, or obligation to another, higher-ranking house.
-
D.
rulingHouse
Indicates that one entity serves as the dynastic or noble family that holds ruling authority over another entity, such as a state, territory, or polity.
-
E.
noble house
Indicates a hierarchical familial or dynastic relationship in which individuals belong to a recognized aristocratic lineage or ruling family.
- F. None of above.
Provenance (3 batches)
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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.