Triple
T8853882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dakota Territory |
E210702
|
entity |
| Predicate | admissionDateOfSuccessorStates |
P47970
|
FINISHED |
| Object | 1889-11-02 |
—
|
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: 1889-11-02 | Statement: [Dakota Territory, admissionDateOfSuccessorStates, 1889-11-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admissionDateOfSuccessorStates Context triple: [Dakota Territory, admissionDateOfSuccessorStates, 1889-11-02]
-
A.
dateOfSuccession
chosen
Indicates the specific date on which one entity formally succeeded or took over a role, position, or title from another.
-
B.
successorAdoptionYear
Indicates the year in which a successor entity formally adopted or took over from its predecessor.
-
C.
laterAdministrativeSuccessor
Indicates that one administrative entity succeeds another in governing authority or jurisdiction at a later time.
-
D.
successorOfficeEstablished
Indicates that a new office or position was formally created to replace or succeed a previous one.
-
E.
successorOfficeOfCoSovereign
Indicates that one office is the subsequent or replacement office to a previous co-sovereign office in a line of succession.
- 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60c6dce88190b175698b191fb89b |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:49 p.m.