Triple
T14208298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Reyne of Castamere |
E352157
|
entity |
| Predicate | familyFate |
P113213
|
FINISHED |
| Object | entire line exterminated |
—
|
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: entire line exterminated | Statement: [House Reyne of Castamere, familyFate, entire line exterminated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyFate Context triple: [House Reyne of Castamere, familyFate, entire line exterminated]
-
A.
enemyFamily
Indicates that two entities belong to families that are hostile or in conflict with each other.
-
B.
familia
Indicates a familial relationship or bond between entities, such as being members of the same family.
-
C.
familyAlliance
Indicates a cooperative or supportive relationship formed between families, often involving mutual obligations, shared interests, or joint actions.
-
D.
family
Indicates a familial relationship or connection between entities, such as being related by blood, marriage, or adoption.
-
E.
familyGroup
Indicates that multiple entities are related to each other as members of the same family unit or household.
- F. None of above. chosen
Provenance (4 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61fa8d24819092a8ec5d34c1c799 |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:05 a.m.