Triple
T4545278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O.Ont |
E110029
|
entity |
| Predicate | hasHonorRank |
P301
|
FINISHED |
| Object | province’s highest official honour |
—
|
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: province’s highest official honour | Statement: [O.Ont, hasHonorRank, province’s highest official honour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHonorRank Context triple: [O.Ont, hasHonorRank, province’s highest official honour]
-
A.
honorLevel
Indicates the degree or status of respect, distinction, or recognition accorded to an entity relative to others.
-
B.
hasHonoraryMember
Indicates that an entity is recognized as an honorary (non-regular) member of another entity, typically without full rights or obligations of standard membership.
-
C.
hasHonorificStatus
Indicates that an entity holds or is assigned a particular honorific title, rank, or status in relation to another entity.
-
D.
hasNotableHonor
Indicates that an entity has received a significant award, title, or formal recognition of distinction.
-
E.
honorificRank
chosen
Indicates that one entity holds a formal title or honorific status 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57d62a8481909d5d803a582c76a1 |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:05 p.m.