Triple
T22510448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1988 Chilean national plebiscite |
E556503
|
entity |
| Predicate | percentageForYes |
P80316
|
FINISHED |
| Object | 44.01% |
—
|
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: 44.01% | Statement: [1988 Chilean national plebiscite, percentageForYes, 44.01%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: percentageForYes Context triple: [1988 Chilean national plebiscite, percentageForYes, 44.01%]
-
A.
votesForPercentage
chosen
Indicates the proportion of total votes that one entity receives in favor of another entity or option, usually expressed as a percentage.
-
B.
percentage
Indicates the proportion or share of one quantity relative to another, typically expressed as a value out of 100.
-
C.
noVotesPercentage
Indicates the proportion of total votes that were cast as "no" in a given decision or election.
-
D.
supportPercentage
Indicates the proportion or share of total backing, approval, or assistance that one entity provides to or receives from another, typically expressed as a percentage.
-
E.
voterTurnoutPercentage
Indicates the proportion of eligible or registered voters who actually cast a ballot in a given election, expressed as a percentage.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d5faf6c8190ba0513be9ae7d128 |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.