Triple
T27864258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Warrant of 1917 |
E704312
|
entity |
| Predicate | honoursMilitaryService |
P164356
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Royal Warrant of 1917, honoursMilitaryService, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honoursMilitaryService Context triple: [Royal Warrant of 1917, honoursMilitaryService, yes]
-
A.
honoursCivilianService
Indicates recognition or commemoration of an individual's non-military contributions or service to society.
-
B.
militaryAward
Indicates that an entity has received or been granted a specific military honor, decoration, or award.
-
C.
highestMilitaryDecoration
Indicates that the object is the most prestigious military award or honor that has been conferred upon the subject.
-
D.
isGallantryAward
Indicates that the subject is a formal gallantry award, i.e., an honor conferred in recognition of exceptional bravery or valor.
-
E.
honourOf
Indicates that one entity is the source, bearer, or cause of another entity’s honor, prestige, or distinguished recognition.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 6:19 p.m.