Triple
T36584113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma Enabling Act |
E902475
|
entity |
| Predicate | setRequirement |
P39303
|
FINISHED |
| Object | approval of the Oklahoma constitution by popular vote |
—
|
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: approval of the Oklahoma constitution by popular vote | Statement: [Oklahoma Enabling Act, setRequirement, approval of the Oklahoma constitution by popular vote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setRequirement Context triple: [Oklahoma Enabling Act, setRequirement, approval of the Oklahoma constitution by popular vote]
-
A.
setupRequirement
Indicates that one entity specifies a prerequisite or condition that must be fulfilled before another entity can be set up or initialized.
-
B.
establishedRequirement
chosen
Indicates that one entity has formally set or defined a requirement that another entity is expected to satisfy or comply with.
-
C.
componentRequirement
Indicates that one component depends on or necessitates the presence or use of another component to function or be considered complete.
-
D.
projectRequirement
Indicates that one entity specifies a necessary condition, resource, or criterion that must be satisfied for a project associated with another entity.
-
E.
planningRequirement
Indicates that one entity imposes or specifies a planning-related obligation, condition, or prerequisite that must be satisfied by another entity or activity.
- 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.