Triple
T27712121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1962 Canadian federal election |
E698717
|
entity |
| Predicate | leader1Riding |
P162970
|
FINISHED |
| Object | Prince Albert |
—
|
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: Prince Albert | Statement: [1962 Canadian federal election, leader1Riding, Prince Albert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leader1Riding Context triple: [1962 Canadian federal election, leader1Riding, Prince Albert]
-
A.
firstRider
Indicates that one entity is the first rider in relation to another entity, typically marking the earliest or primary participant in a riding-related context.
-
B.
leader2
Indicates that one entity serves as a leader, chief, or primary authority figure in relation to another entity.
-
C.
famousRider
Indicates that an entity is a rider who is widely known or celebrated.
-
D.
riderType
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
-
E.
notableRiderType
Indicates that an entity is notably associated with a particular type or category of rider (e.g., cyclist, jockey, driver).
- 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_69f635cc45fc8190b8e8a2734b0b69ee |
completed | May 2, 2026, 5:35 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f6305219f08190b55f6193a4a49984 |
completed | May 2, 2026, 5:11 p.m. |
Created at: April 27, 2026, 3:02 p.m.