Triple
T35051308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Era of Tamriel |
E1011335
|
entity |
| Predicate | endRuler |
P48946
|
FINISHED |
| Object | Martin Septim |
—
|
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: Martin Septim | Statement: [Third Era of Tamriel, endRuler, Martin Septim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endRuler Context triple: [Third Era of Tamriel, endRuler, Martin Septim]
-
A.
endOfDirectLineRuler
Indicates that one entity is the final ruler in a continuous, unbroken line of direct succession from another entity.
-
B.
endRule
Indicates that a previously active rule, regulation, or governing condition is terminated or ceases to apply.
-
C.
finalRuler
chosen
Indicates that an entity is the last or ultimate ruler of another entity, with no subsequent rulers following.
-
D.
recognizedAsRuler
Indicates that one entity is acknowledged or accepted by others as the legitimate ruler or sovereign authority.
-
E.
providedRulerFor
Indicates that one entity supplied or designated another entity to serve as the ruler or governing authority over a particular domain or group.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f785ce33448190bb40272ccb52ccda |
completed | May 3, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.