Triple
T29490842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okmulgee County |
E748072
|
entity |
| Predicate | hasStateLegislativeBody |
P170172
|
FINISHED |
| Object | Oklahoma Legislature |
—
|
NE NERFINISHED |
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: Oklahoma Legislature | Statement: [Okmulgee County, hasStateLegislativeBody, Oklahoma Legislature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStateLegislativeBody Context triple: [Okmulgee County, hasStateLegislativeBody, Oklahoma Legislature]
-
A.
isInStateLegislativeBody
Indicates that an entity serves as a member of a state-level legislative body or assembly.
-
B.
hasLegislativeState
Indicates that an entity is associated with, governed by, or falls under the jurisdiction of a particular legislative state or lawmaking authority.
-
C.
isPartOfStateLegislature
Indicates that an entity serves as a member or component within a specific state-level legislative body.
-
D.
isLegislativeBody
Indicates that the subject entity functions as an official law-making or legislative body within a political or organizational system.
-
E.
legislativeBodyWith
chosen
Indicates that one entity serves as the legislative body associated with, or having authority over, another entity.
- 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_69f0bd448c6881908aa6b475cefd5ddc |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: April 28, 2026, 4:13 p.m.