Triple
T28077894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saar Statute |
E709594
|
entity |
| Predicate | rejectionPercentageYesVote |
P164562
|
FINISHED |
| Object | approximately 33 percent |
—
|
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: approximately 33 percent | Statement: [Saar Statute, rejectionPercentageYesVote, approximately 33 percent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rejectionPercentageYesVote Context triple: [Saar Statute, rejectionPercentageYesVote, approximately 33 percent]
-
A.
referendumYesPercentage
Indicates the percentage of votes cast in favor of the "yes" option in a referendum.
-
B.
noVotesPercentage
Indicates the proportion of total votes that were cast as "no" in a given decision or election.
-
C.
totalRejectedBallots
Indicates the number of ballots that were submitted but not accepted or counted in an election or voting process.
-
D.
votersCouldRejectList
Indicates that voters have the option or authority to reject a proposed list (such as a candidate list or item list) rather than accept or select from it.
-
E.
voterApproval
Indicates that a voter has given consent, support, or positive endorsement to a proposal, candidate, or decision.
- F. None of above. chosen
Provenance (4 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 8:50 p.m.