Triple
T911856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri |
E19676
|
entity |
| Predicate | admittedAs |
P6135
|
FINISHED |
| Object | 24th state of the United States |
—
|
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: 24th state of the United States | Statement: [Missouri, admittedAs, 24th state of the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admittedAs Context triple: [Missouri, admittedAs, 24th state of the United States]
-
A.
admittedState
Indicates that an entity has been formally accepted or allowed into a particular state or condition.
-
B.
admittedToUnionAs
chosen
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.
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.
-
D.
adoptedAs
Indicates that one entity has taken another into its family or care through a formal or recognized adoption process.
-
E.
admissionOrder
Indicates the sequence or priority in which admissions occur or are processed relative to one another.
- 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_69a4939f91a08190ba68c2c81eab90fe |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b2f605bc8190a5245aa2ca55cf43 |
completed | March 1, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69a4b2918ea881908698020b995a8eae |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:39 p.m.