Triple
T13376093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Saxe-Altenburg |
E319187
|
entity |
| Predicate | lastRulerEndTime |
P24460
|
FINISHED |
| Object | 1918 |
—
|
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: 1918 | Statement: [Duchy of Saxe-Altenburg, lastRulerEndTime, 1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastRulerEndTime Context triple: [Duchy of Saxe-Altenburg, lastRulerEndTime, 1918]
-
A.
hasLastRuler
Indicates that a specified entity is the final or most recent ruler of another entity (such as a state, dynasty, or territory).
-
B.
lastRun
Indicates the most recent time or instance at which a particular process, task, or action was executed.
-
C.
latestTime
chosen
Indicates the most recent point in time at which the related event, state, or condition occurs or is valid among a set of possible times.
-
D.
finalRuler
Indicates that an entity is the last or ultimate ruler of another entity, with no subsequent rulers following.
-
E.
lastRulerBeforeAnnexation
Indicates that the subject was the final sovereign ruler of a polity immediately prior to its annexation by another power or state.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadce3fec48190a5443d87c85477a3 |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:33 p.m.