Triple
T27712134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1962 Canadian federal election |
E698717
|
entity |
| Predicate | leader2Swing |
P167130
|
FINISHED |
| Object | +4.0 percentage points |
—
|
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: +4.0 percentage points | Statement: [1962 Canadian federal election, leader2Swing, +4.0 percentage points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leader2Swing Context triple: [1962 Canadian federal election, leader2Swing, +4.0 percentage points]
-
A.
leader1Swing
Indicates that the first leader performs or initiates a swinging action in relation to another entity or context.
-
B.
leader2
Indicates that one entity serves as a leader, chief, or primary authority figure in relation to another entity.
-
C.
leaderClass
Indicates that one entity serves as the primary leader or head within a specified class, group, or category of entities.
-
D.
bandLeader
Indicates that one entity serves as the leader or primary directing figure of a musical band that includes the other entity.
-
E.
houseBandLeader
Indicates that one entity serves as the leader of a house band associated with another entity (such as a venue, show, or organization).
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 27, 2026, 3:02 p.m.