Triple
T38240918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragonpit |
E1013756
|
entity |
| Predicate | statusAfterTargaryens |
P201616
|
FINISHED |
| Object | abandoned |
—
|
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: abandoned | Statement: [Dragonpit, statusAfterTargaryens, abandoned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterTargaryens Context triple: [Dragonpit, statusAfterTargaryens, abandoned]
-
A.
statusDuringTargaryenConquest
Indicates the role, condition, or standing an entity held specifically during the period of the Targaryen Conquest.
-
B.
loyaltyAfterDaenerysDeath
Indicates that one entity remains loyal to another specifically after Daenerys’s death.
-
C.
lostThronesAfter
Indicates that one or more entities ceased to hold their thrones or ruling positions after a specified event, time, or condition.
-
D.
predecessorAtCasterlyRock
Indicates that one entity previously held a position or role at Casterly Rock before another entity.
-
E.
predecessorOnDragonstone
Indicates that one entity previously held a position, role, or status on Dragonstone 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_6a000be59ad88190a6aa3a42c097796d |
completed | May 10, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_6a000ab6e9bc81908300b81d004e5921 |
completed | May 10, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_6a000be4d3f48190bdecd0a044a0e453 |
completed | May 10, 2026, 4:39 a.m. |
Created at: May 3, 2026, 4:30 p.m.