Triple
T3323378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queensland state elections |
E69850
|
entity |
| Predicate | votingOptions |
P2726
|
FINISHED |
| Object | in-person voting |
—
|
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: in-person voting | Statement: [Queensland state elections, votingOptions, in-person voting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingOptions Context triple: [Queensland state elections, votingOptions, in-person voting]
-
A.
votingMethod
chosen
Indicates the procedure or system by which a vote is cast, collected, and counted in a decision-making or electoral process.
-
B.
votingControl
Indicates that one entity has the power to determine or significantly influence the outcome of decisions made by another entity through its voting rights.
-
C.
votingBasis
Indicates the principle, criterion, or grounds on which a vote or voting decision is made.
-
D.
voteType
Indicates the specific category or kind of vote associated with an action or decision (e.g., upvote, downvote, approval, rejection).
-
E.
votingStatus
Indicates whether an entity is currently eligible, registered, or has participated in a voting process.
- 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_69ad85a1829881908942c14075644d0d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb13e6c288190805f8abcd3acc906 |
completed | March 8, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.