Triple
T35118293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andals |
E1014101
|
entity |
| Predicate | descendantGroups |
P36141
|
FINISHED |
| Object | most southern Westerosi nobles |
—
|
LITERAL FINISHED |
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: most southern Westerosi nobles | Statement: [Andals, descendantGroups, most southern Westerosi nobles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: descendantGroups Context triple: [Andals, descendantGroups, most southern Westerosi nobles]
-
A.
descendantGroupRole
Indicates that one group holds a role or position that is hierarchically derived from, or subordinate to, the role of another group in a lineage or inheritance structure.
-
B.
descendantClan
Indicates that one clan is a later-generation offshoot or subordinate lineage that originates from another clan.
-
C.
hasDescendantPeople
chosen
Indicates that one entity has other people as its descendants in a genealogical or lineage-based relationship.
-
D.
successorGroups
Indicates that one group is the direct successor or follow-up group to another group in some sequence or lineage.
-
E.
revealedAsSubgroupOf
Indicates that one group has been newly identified or exposed as being a subgroup or subset of another group.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.