Triple
T38240482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lann the Clever |
E1013747
|
entity |
| Predicate | predecessorAtCasterlyRock |
P197437
|
FINISHED |
| Object | House Casterly |
—
|
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 Casterly | Statement: [Lann the Clever, predecessorAtCasterlyRock, House Casterly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorAtCasterlyRock Context triple: [Lann the Clever, predecessorAtCasterlyRock, House Casterly]
-
A.
predecessorOnDragonstone
Indicates that one entity previously held a position, role, or status on Dragonstone before another entity.
-
B.
predecessorAsLordOfWinterfell
Indicates that one entity previously held the title of Lord of Winterfell immediately before another entity.
-
C.
methodOfGainingCasterlyRock
Indicates the manner or process by which an entity comes to possess or control Casterly Rock.
-
D.
firstBaratheonKing
Indicates that the subject is the first member of House Baratheon to hold the title of king.
-
E.
predecessorAsWarchief
Indicates that one entity previously held the position of warchief immediately before another entity.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
| PDg | Predicate description generation | batch_69fe9137730c81909d1d57c30566c89a |
completed | May 9, 2026, 1:43 a.m. |
Created at: May 3, 2026, 4:30 p.m.