Triple
T27712135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1962 Canadian federal election |
E698717
|
entity |
| Predicate | leader3 |
P20301
|
FINISHED |
| Object | Tommy Douglas |
—
|
NE NERFINISHED |
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: Tommy Douglas | Statement: [1962 Canadian federal election, leader3, Tommy Douglas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leader3 Context triple: [1962 Canadian federal election, leader3, Tommy Douglas]
-
A.
leader2
Indicates that one entity serves as a leader, chief, or primary authority figure in relation to another entity.
-
B.
leaderFrom
Indicates that an entity serves or has served as a leader originating from, representing, or associated with a specified place or organization.
-
C.
mainLeader3
chosen
Indicates that an entity serves as the third primary or most prominent leader within a specified group, organization, or context.
-
D.
leadingOrgan
Indicates that one entity serves as the primary or most responsible organizing body or authority for another entity or activity.
-
E.
leaderSince
Indicates that an entity has held a leadership role over another entity starting from a specified point in time.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 3:02 p.m.