Triple
T33737315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aerys II Targaryen |
E864455
|
entity |
| Predicate | notableKingsguardMember |
P206658
|
FINISHED |
| Object | Jaime Lannister |
E313950
|
NE 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: Jaime Lannister | Statement: [Aerys II Targaryen, notableKingsguardMember, Jaime Lannister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableKingsguardMember Context triple: [Aerys II Targaryen, notableKingsguardMember, Jaime Lannister]
-
A.
firstBaratheonKing
Indicates that the subject is the first member of House Baratheon to hold the title of king.
-
B.
notableServant
Indicates that one entity serves another in a particularly distinguished, prominent, or historically significant capacity.
-
C.
LancastrianCommander
Indicates that the subject serves as a military commander aligned with the Lancastrian side in the Wars of the Roses.
-
D.
GameOfThronesRole
Indicates that one entity plays, voices, or otherwise portrays a character in the television series "Game of Thrones" in relation to another entity.
-
E.
predecessorAsLordOfWinterfell
Indicates that one entity previously held the title of Lord of Winterfell immediately before another entity.
- F. None of above. chosen
Provenance (5 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a366e85f7248190a824fc880fa32a7a |
completed | June 20, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037e07fe4481909ca21eae7a941ee7 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:44 a.m.