Triple
T8163714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Alliance |
E190636
|
entity |
| Predicate | soughtToUnite |
P62056
|
FINISHED |
| Object | Canadian right-of-centre voters |
—
|
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: Canadian right-of-centre voters | Statement: [Canadian Alliance, soughtToUnite, Canadian right-of-centre voters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soughtToUnite Context triple: [Canadian Alliance, soughtToUnite, Canadian right-of-centre voters]
-
A.
aimedToUnify
chosen
Indicates an intention or effort by one entity to bring multiple entities, groups, or elements together into a single unified whole.
-
B.
unites
Indicates that one entity brings together multiple entities into a single, cohesive whole or shared state.
-
C.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
D.
soughtAllianceWith
Indicates that one entity actively attempted to form an alliance or cooperative partnership with another entity.
-
E.
unificationLedTo
Indicates that a process of unifying previously separate entities resulted in or caused a particular outcome or state.
- 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_69ca82c0ef14819083713f4473dd847c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4557ebc88190b4e2cab258374d23 |
completed | March 31, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:38 p.m.