Triple
T32988086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Precedence for Canada |
E844002
|
entity |
| Predicate | secondRankedOffice |
P97688
|
FINISHED |
| Object | governor general of Canada |
—
|
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: governor general of Canada | Statement: [Order of Precedence for Canada, secondRankedOffice, governor general of Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondRankedOffice Context triple: [Order of Precedence for Canada, secondRankedOffice, governor general of Canada]
-
A.
secondRank
chosen
Indicates that one entity holds the second position or rank in order or hierarchy relative to others.
-
B.
fourthRankedOffice
Indicates that one office holds the fourth position in a ranking or ordered hierarchy relative to other offices.
-
C.
secondRankSee
Indicates that a second-ranked entity observes, notices, or visually perceives another entity.
-
D.
secondOfficeholderStart
Indicates the date or point in time when the second person to hold a particular office or position began their term.
-
E.
secondLeader
Indicates that an entity serves as the second-ranking leader or deputy leader in relation to another entity.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69febce5877c8190a5e000ef5331ec88 |
completed | May 9, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69febad1cd588190abc7686bcb39a371 |
completed | May 9, 2026, 4:40 a.m. |
Created at: May 1, 2026, 1:22 a.m.