Triple
T27712137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1962 Canadian federal election |
E698717
|
entity |
| Predicate | leader3Riding |
P168089
|
FINISHED |
| Object | Regina City |
—
|
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: Regina City | Statement: [1962 Canadian federal election, leader3Riding, Regina City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leader3Riding Context triple: [1962 Canadian federal election, leader3Riding, Regina City]
-
A.
leader2Riding
Indicates that the second leader is engaged in the act of riding something or someone.
-
B.
leader1Riding
Indicates that the first leader is mounted on and riding another entity (such as an animal or vehicle).
-
C.
riderType
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
-
D.
leader2
Indicates that one entity serves as a leader, chief, or primary authority figure in relation to another entity.
-
E.
primaryRiders
Indicates that the referenced entities are the main or principal riders associated with a particular vehicle, trip, or ride-related event.
- 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_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 27, 2026, 3:02 p.m.