Triple
T293671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of Chile |
E6046
|
entity |
| Predicate | electionSystemForHead |
P539
|
FINISHED |
| Object | direct 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: direct popular vote | Statement: [Government of Chile, electionSystemForHead, direct popular vote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electionSystemForHead Context triple: [Government of Chile, electionSystemForHead, direct popular vote]
-
A.
electionMethod
chosen
Indicates the process or system used to select a candidate or make a decision in an election.
-
B.
electedCandidate
Indicates that a particular person has been chosen as the winner in an election for a given position or office.
-
C.
headOfGovernmentChosenBy
Indicates that the head of government is selected or appointed through the decision or authority of the specified chooser.
-
D.
electedWith
Indicates that one entity attained an elected position or office together with, or as part of the same electoral outcome as, another entity.
-
E.
electoralBody
Indicates that an entity functions as an official body responsible for overseeing, administering, or making decisions related to elections for 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea0dd1dc8190aecd5afdeb2fd74b |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e934b4408190b53a17f57a02df65 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.