Triple
T8711691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of New Zealand |
E206790
|
entity |
| Predicate | typeOfServiceRecognised |
P849
|
FINISHED |
| Object | service to the Crown |
—
|
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: service to the Crown | Statement: [Order of New Zealand, typeOfServiceRecognised, service to the Crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfServiceRecognised Context triple: [Order of New Zealand, typeOfServiceRecognised, service to the Crown]
-
A.
scopeOfServiceRecognized
Indicates that the extent or range of services provided has been formally acknowledged or accepted.
-
B.
typeOfServiceRegulated
Indicates that a particular type of service is subject to regulation or oversight under a specified regulatory framework or authority.
-
C.
hasServiceType
chosen
Indicates that an entity is associated with or categorized by a particular type of service.
-
D.
appliesToServiceType
Indicates that something is relevant or applicable specifically to a particular type or category of service.
-
E.
areRecognizedBy
Indicates that one entity acknowledges, identifies, or accepts another entity as valid, known, or legitimate.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5c3189f88190bb9bb77ba9d28d60 |
completed | March 31, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.