Triple
T13440936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Territory South of the River Ohio |
E320356
|
entity |
| Predicate | statehoodOrder |
P109945
|
FINISHED |
| Object | 16th state |
—
|
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: 16th state | Statement: [Territory South of the River Ohio, statehoodOrder, 16th state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statehoodOrder Context triple: [Territory South of the River Ohio, statehoodOrder, 16th state]
-
A.
statehoodStatus
Indicates the legal or political condition of an entity regarding whether, how, or to what extent it is recognized or functions as a state.
-
B.
statehoodContext
Indicates the contextual circumstances, conditions, or framework under which an entity’s status as a state (or its statehood) is defined, recognized, or discussed.
-
C.
statehoodYear
Indicates the year in which an entity officially became a recognized state or attained statehood status.
-
D.
statehoodFrom
Indicates the point in time from which an entity has held official statehood or recognized status as a state.
-
E.
statehoodEvent
Indicates an event or process through which an entity attains, changes, or loses the status of being a recognized state.
- F. None of above. chosen
Provenance (4 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaee704ac8190b4c7f4e0d3a88494 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:40 p.m.