Triple
T21607441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canada–United Kingdom relations |
E533213
|
entity |
| Predicate | usesDiplomaticTitle |
P2097
|
FINISHED |
| Object | High Commissioner |
—
|
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: High Commissioner | Statement: [Canada–United Kingdom relations, usesDiplomaticTitle, High Commissioner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDiplomaticTitle Context triple: [Canada–United Kingdom relations, usesDiplomaticTitle, High Commissioner]
-
A.
usesRoyalTitle
Indicates that one entity refers to another using a royal title or honorific (such as king, queen, prince, or similar).
-
B.
officeHolderMayUseTitle
Indicates that a person who holds a particular office is permitted to use a specified official title.
-
C.
usedForDiplomaticHonours
Indicates that something is employed as a means of conferring or expressing diplomatic honors or recognition between parties.
-
D.
hasDiplomaticRankHead
Indicates that an entity serving as a head (e.g., of a mission or organization) holds a specific diplomatic rank.
-
E.
honorificTitle
chosen
Indicates that one entity serves as a formal honorific or respectful title used to address or refer 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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef17e6378881908678dc903b8ba6ac |
completed | April 27, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:33 p.m.