Triple
T11184500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Territory |
E264626
|
entity |
| Predicate | admissionToUnionAsState |
P11034
|
FINISHED |
| Object | 1889-11-11 |
—
|
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-11 | Statement: [Washington Territory, admissionToUnionAsState, 1889-11-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admissionToUnionAsState Context triple: [Washington Territory, admissionToUnionAsState, 1889-11-11]
-
A.
admittedToUnionAsStateNumber
Indicates the ordinal position at which an entity (typically a U.S. state) was formally admitted into a political union as a state.
-
B.
succeededToStatehoodAs
Indicates that one entity became a sovereign state as the direct successor to another entity’s prior political or territorial status.
-
C.
statehoodEvent
Indicates an event or process through which an entity attains, changes, or loses the status of being a recognized state.
-
D.
admittedAsCountyWithStatehood
Indicates that an entity became a county at the same time its encompassing state was granted statehood.
-
E.
statehoodYear
chosen
Indicates the year in which an entity officially became a recognized state or attained statehood status.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8a9c5e081908c85b41a268428fb |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.