Triple
T31306321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee |
E798343
|
entity |
| Predicate | readmittedToUnion |
P205
|
FINISHED |
| Object | 1866 |
—
|
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: 1866 | Statement: [Tennessee, readmittedToUnion, 1866]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readmittedToUnion Context triple: [Tennessee, readmittedToUnion, 1866]
-
A.
admittedToUnionFrom
Indicates that an entity (such as a state or region) was admitted into a union or larger political entity from a specified prior jurisdiction or status.
-
B.
admittedToUnionAs
Indicates that an entity (typically a state or region) was formally accepted and incorporated into a political union or federation in a specified capacity or status.
-
C.
admittedToUnionOn
chosen
Indicates that an entity (typically a state or region) was formally accepted and incorporated into a union or federation on a specific date.
-
D.
previouslyAdmitted
Indicates that an entity has already been admitted or accepted at an earlier time prior to the current reference point.
-
E.
reenteredWith
Indicates that an entity entered a place or state again while accompanied by, or in conjunction with, another specified entity.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:14 p.m.