Triple
T18338076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | President of the Privy Council (Canada) |
E439324
|
entity |
| Predicate | typeOfCouncilPresided |
P21035
|
FINISHED |
| Object | privy council |
—
|
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: privy council | Statement: [President of the Privy Council (Canada), typeOfCouncilPresided, privy council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCouncilPresided Context triple: [President of the Privy Council (Canada), typeOfCouncilPresided, privy council]
-
A.
councilPresidedOverBy
Indicates that a council or formal assembly is led, directed, or overseen by a particular person or authority.
-
B.
councilType
chosen
Indicates the specific kind or classification of a council that an entity is associated with or designated as.
-
C.
roleInCouncil
Indicates that an entity holds a specific position or function within a council or governing body.
-
D.
councilConvokedBy
Indicates that a council or formal assembly was called together or convened by a particular person, group, or authority.
-
E.
seatOfCouncil
Indicates that a location serves as the official meeting place or headquarters of a council.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50ecf3b4c81909372630ab634dd43 |
completed | April 19, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:37 a.m.