Triple
T26552311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of Coahuila |
E671710
|
entity |
| Predicate | electoralSystemForGovernor |
P90693
|
FINISHED |
| Object | 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: popular vote | Statement: [Government of Coahuila, electoralSystemForGovernor, popular vote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electoralSystemForGovernor Context triple: [Government of Coahuila, electoralSystemForGovernor, popular vote]
-
A.
governorSelectionMethod
chosen
Indicates the method or process by which a governor is chosen or comes into office.
-
B.
governorateSystem
Indicates a system in which a territory or region is organized, administered, or governed as a governorate.
-
C.
electoralSystemForLegislature
Indicates the type of electoral system used to choose members of a particular legislature.
-
D.
electoralSystemAtCreation
Indicates the type of electoral system that was in place at the time an entity (such as a political body or office) was originally established.
-
E.
governorateType
Indicates the specific classification or category of a governorate within an administrative or governmental hierarchy.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 27, 2026, 1:48 a.m.