Triple
T6768223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1984 Canadian federal election |
E154976
|
entity |
| Predicate | secondPartySeatChange |
P73162
|
FINISHED |
| Object | -95 |
—
|
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: -95 | Statement: [1984 Canadian federal election, secondPartySeatChange, -95]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondPartySeatChange Context triple: [1984 Canadian federal election, secondPartySeatChange, -95]
-
A.
transferredSeatsTo
Indicates that one entity moved or reassigned seats it controlled or possessed to another entity.
-
B.
AllianceSeatChange
Indicates a change in a party’s or member’s seat allocation resulting from forming, joining, leaving, or reconfiguring a political alliance.
-
C.
hasSecondSeat
Indicates that an entity possesses or includes a secondary seat in addition to a primary one.
-
D.
otherSeat
Indicates that one entity is the alternative or different seat relative to another seat in a given context.
-
E.
laterSeat
Indicates that one entity is seated in a position that comes after another entity in a specified ordering or sequence of seats.
- 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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d231b79c81908a4f7fa8f253706d |
completed | March 27, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69c6d094105881909c5806eb4afa6306 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1d5f1908190989efc8a2d18c965 |
completed | March 27, 2026, 6:52 p.m. |
Created at: March 27, 2026, 2:12 p.m.