Triple
T19124434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1999 Australian republic referendum |
E468138
|
entity |
| Predicate | yesVoteNational |
P86317
|
FINISHED |
| Object | approximately 45.13% |
—
|
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 45.13% | Statement: [1999 Australian republic referendum, yesVoteNational, approximately 45.13%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yesVoteNational Context triple: [1999 Australian republic referendum, yesVoteNational, approximately 45.13%]
-
A.
yesVotes
Indicates that a specified entity has cast or received affirmative votes in a decision-making or voting context.
-
B.
yesVoteShareQuestion1
chosen
Indicates the proportion of total votes that were cast as "yes" in response to question 1.
-
C.
yesVoteShareQuestion2
Indicates the proportion of total votes cast in favor of the "Yes" option on question 2 of a ballot or survey.
-
D.
voteFor
Indicates that one entity casts or expresses a vote in favor of another entity or option.
-
E.
vote
Indicates that an entity formally expresses a choice or preference in a decision-making process, typically an election or poll.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3cb9d6c81908a8706c1f33a6378 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.