Triple
T8211707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Speaker of the House of Commons of Canada |
E191830
|
entity |
| Predicate | votesOnly |
P81518
|
FINISHED |
| Object | to break a tie |
—
|
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: to break a tie | Statement: [Speaker of the House of Commons of Canada, votesOnly, to break a tie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votesOnly Context triple: [Speaker of the House of Commons of Canada, votesOnly, to break a tie]
-
A.
voteCount
Indicates the number of votes that have been cast for or associated with a particular item or option.
-
B.
voteType
Indicates the specific category or kind of vote associated with an action or decision (e.g., upvote, downvote, approval, rejection).
-
C.
yesVotes
Indicates that a specified entity has cast or received affirmative votes in a decision-making or voting context.
-
D.
voteRecord
Indicates that an entity has cast a specific vote or holds a particular voting position in a given decision or election.
-
E.
voteFor
Indicates that one entity casts or expresses a vote in favor of another entity or option.
- 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb76dec42c819090252fe186a68d34 |
completed | March 31, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb4ab5162c8190bddd696078689895 |
completed | March 31, 2026, 4:16 a.m. |
Created at: March 30, 2026, 5:44 p.m.