Triple
T712009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Constitution |
E14229
|
entity |
| Predicate | statehoodContext |
P19781
|
FINISHED |
| Object | Oregon statehood |
—
|
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: Oregon statehood | Statement: [Oregon Constitution, statehoodContext, Oregon statehood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statehoodContext Context triple: [Oregon Constitution, statehoodContext, Oregon statehood]
-
A.
statehoodFrom
Indicates the point in time from which an entity has held official statehood or recognized status as a state.
-
B.
statehoodYear
Indicates the year in which an entity officially became a recognized state or attained statehood status.
-
C.
sovereigntyStatus
Indicates the degree and type of political independence or control an entity holds over its own territory and governance.
-
D.
states
Indicates that an entity formally declares, expresses, or asserts a fact, opinion, or condition about another entity or situation.
-
E.
sovereignState
Indicates that an entity is recognized as an independent, self-governing state with ultimate authority over its territory and not subject to any higher political power.
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a77fcc6881908a025bb21e44ad56 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f221b081909fbaa689fb20eb3e |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a77e42e081909a6f2d1bfdc78ef0 |
completed | March 1, 2026, 8:54 p.m. |
Created at: March 1, 2026, 7:36 p.m.