Triple
T35531216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaehaerys I Targaryen |
E1026804
|
entity |
| Predicate | houseAlliance |
P600
|
FINISHED |
| Object | House Velaryon |
—
|
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 Velaryon | Statement: [Jaehaerys I Targaryen, houseAlliance, House Velaryon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseAlliance Context triple: [Jaehaerys I Targaryen, houseAlliance, House Velaryon]
-
A.
houseSeatAllegiance
Indicates that a noble house holds loyalty or sworn allegiance to a particular higher authority, such as a liege, faction, or realm.
-
B.
homeFaction
Indicates the faction or group to which an entity primarily belongs or is originally affiliated.
-
C.
alliance
chosen
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
D.
vassalHouse
Indicates a feudal or subordinate relationship in which one house is bound in loyalty, service, or obligation to another, higher-ranking house.
-
E.
houseAffiliation
Indicates the association or belonging of an entity to a particular house or household.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:04 p.m.