Triple
T27153307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edmonton (federal electoral district) |
E682448
|
entity |
| Predicate | usesVotersList |
P82924
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Edmonton (federal electoral district), usesVotersList, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVotersList Context triple: [Edmonton (federal electoral district), usesVotersList, yes]
-
A.
usesVoterLists
chosen
Indicates that one entity employs or relies on voter registration lists in relation to another entity or activity.
-
B.
containsVotersFrom
Indicates that one entity includes or encompasses voters originating from another entity.
-
C.
usesVoterRegistration
Indicates that one entity relies on or applies another entity’s voter registration information for a particular purpose or process.
-
D.
usesVotingBallots
Indicates that one entity conducts or participates in a voting process by employing ballots as the method for casting votes.
-
E.
usesVotingBody
Indicates that one entity employs or relies on a particular voting body to make decisions or take actions on its behalf.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 9:15 a.m.