Triple
T9509558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of British Columbia |
E229355
|
entity |
| Predicate | fieldOfEndeavour |
P54903
|
FINISHED |
| Object | public service |
—
|
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: public service | Statement: [Order of British Columbia, fieldOfEndeavour, public service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldOfEndeavour Context triple: [Order of British Columbia, fieldOfEndeavour, public service]
-
A.
fieldOfSignificance
chosen
Indicates that something holds particular importance, relevance, or impact within a specified domain, context, or area of interest.
-
B.
fieldOfWork
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
C.
careerField
Indicates the professional domain or occupational area in which an entity works or specializes.
-
D.
regionOfAcademicInterest
Indicates that an entity has a particular academic field or subject area as its focus of interest or study.
-
E.
regionOfAcademicFocus
Indicates the academic subject area or discipline that an entity (such as a person or program) primarily concentrates on or specializes in.
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9857058881909e0a40e2024a7b4c |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:58 p.m.