Triple
T7077460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunflower State |
E164854
|
entity |
| Predicate | hasStatehoodDateOfReferent |
P14008
|
FINISHED |
| Object | January 29, 1861 |
—
|
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: January 29, 1861 | Statement: [Sunflower State, hasStatehoodDateOfReferent, January 29, 1861]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatehoodDateOfReferent Context triple: [Sunflower State, hasStatehoodDateOfReferent, January 29, 1861]
-
A.
statehoodYear
Indicates the year in which an entity officially became a recognized state or attained statehood status.
-
B.
statehoodFrom
chosen
Indicates the point in time from which an entity has held official statehood or recognized status as a state.
-
C.
sovereignStateUntil
Indicates that an entity functioned as a sovereign state up to a specified end time or date.
-
D.
countryEstablishedFor
Indicates that a country was founded, created, or formally established for the benefit, purpose, or use of a particular entity or group.
-
E.
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.
- 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_69c6887cbc6c8190bdfac42d940f4d8a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4ee29288190a9a3fa7a6c713d8f |
completed | March 27, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:40 p.m.