Triple
T23409584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article IV of the Missouri Constitution |
E560028
|
entity |
| Predicate | definesVetoPowerOf |
P72417
|
FINISHED |
| Object | Governor of Missouri |
—
|
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: Governor of Missouri | Statement: [Article IV of the Missouri Constitution, definesVetoPowerOf, Governor of Missouri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesVetoPowerOf Context triple: [Article IV of the Missouri Constitution, definesVetoPowerOf, Governor of Missouri]
-
A.
hasVetoPower
chosen
Indicates that one entity possesses the authority to unilaterally reject or block decisions, actions, or proposals made by another entity or group.
-
B.
vetoType
Indicates the specific kind or category of veto applied in a decision-making or approval process.
-
C.
vetoedBy
Indicates that an action, decision, or proposal was rejected or blocked by a specific entity with veto authority.
-
D.
hasLegislativePower
Indicates that an entity possesses the authority to create, amend, or repeal laws within a given jurisdiction or governing framework.
-
E.
votingPowerPerSenator
Indicates the amount of voting influence or weight assigned to each individual senator in a decision-making process.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a50fff10819094e71fb0c11b7d95 |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:38 p.m.