Triple
T28413722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen’s Service Order |
E719739
|
entity |
| Predicate | hasRelatedHonour |
P199741
|
FINISHED |
| Object | Queen’s Service Medal |
—
|
NE NERFINISHED |
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: Queen’s Service Medal | Statement: [Queen’s Service Order, hasRelatedHonour, Queen’s Service Medal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatedHonour Context triple: [Queen’s Service Order, hasRelatedHonour, Queen’s Service Medal]
-
A.
belongsToHonoursSystem
Indicates that something is a component or member of a specific honours or awards system.
-
B.
hasNotableHonor
Indicates that an entity has received a significant award, title, or formal recognition of distinction.
-
C.
hasCodeOfHonor
Indicates that an entity adheres to a personal or shared ethical code that guides its behavior and decisions.
-
D.
hasRankInNewZealandHonoursSystem
Indicates that an entity holds a specific rank or level within the New Zealand Honours System.
-
E.
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.
- F. None of above. chosen
Provenance (4 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69ff53389a0481908b2baeb43c6294f0 |
completed | May 9, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69ff52e2b4b88190b38d160d771fe14b |
completed | May 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69ff5337e6f88190ae0418335477063c |
completed | May 9, 2026, 3:31 p.m. |
Created at: April 28, 2026, 1:28 a.m.