Triple
T8083836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Senate elections |
E188680
|
entity |
| Predicate | ballotSecrecy |
P53148
|
FINISHED |
| Object | secret ballot |
—
|
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: secret ballot | Statement: [Australian Senate elections, ballotSecrecy, secret ballot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballotSecrecy Context triple: [Australian Senate elections, ballotSecrecy, secret ballot]
-
A.
ballotSecrecyEnforcedBy
Indicates that measures or mechanisms are in place to ensure the secrecy of voters’ ballots is protected by a specified actor, process, or system.
-
B.
ballotSecret
chosen
Indicates that the contents of a ballot are kept confidential and cannot be linked back to the individual who cast it.
-
C.
ballot
Indicates that an entity participates in a formal voting process, typically by casting or submitting a vote or choice.
-
D.
ballotStructure
Indicates how options, candidates, or choices are organized and presented on a ballot for selection.
-
E.
ballotStatus
Indicates the current state or outcome of a ballot within a voting or decision-making 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb415e61ac81909e924aea69a7ff77 |
completed | March 31, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:29 p.m.