Triple
T19162084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Political Reform Act of 1976 |
E469079
|
entity |
| Predicate | turnoutInReferendum |
P1234
|
FINISHED |
| Object | high voter turnout |
—
|
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: high voter turnout | Statement: [Political Reform Act of 1976, turnoutInReferendum, high voter turnout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turnoutInReferendum Context triple: [Political Reform Act of 1976, turnoutInReferendum, high voter turnout]
-
A.
referendumResult
Indicates the outcome or decision reached by voters in a specific referendum.
-
B.
referendumYesPercentage
Indicates the percentage of votes cast in favor of the "yes" option in a referendum.
-
C.
heldReferendum
Indicates that an entity organized and conducted a referendum, typically allowing eligible participants to vote directly on a specific issue or proposal.
-
D.
referendumHeldAmong
Indicates that a referendum was conducted among a specified group or population as the decision-making body.
-
E.
voterTurnoutPercentage
chosen
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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eebe03ac8190bbe0b34ebf0d90c6 |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.