Triple
T35011497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dwemer |
E1009947
|
entity |
| Predicate | lastKnownSurvivor |
P19817
|
FINISHED |
| Object | Yagrum Bagarn |
—
|
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: Yagrum Bagarn | Statement: [Dwemer, lastKnownSurvivor, Yagrum Bagarn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastKnownSurvivor Context triple: [Dwemer, lastKnownSurvivor, Yagrum Bagarn]
-
A.
lastKnownSurvivorDiedIn
Indicates that the final remaining survivor associated with something died in a specified place or event.
-
B.
isSurvivorOf
Indicates that one entity has lived through, endured, or remained alive after a particular event, condition, or harmful circumstance involving another entity.
-
C.
lastRemnantOf
chosen
Indicates that one entity is the sole remaining instance or surviving part of another entity, after all similar or related instances have disappeared.
-
D.
lastHeir
Indicates that one entity is the final remaining heir in a line of succession to another entity’s estate, title, or inheritance.
-
E.
survivingPerpetrators
Indicates that the referenced individuals are perpetrators of an act or event who are still alive following that act or event.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
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.