Triple
T689933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Distinguished Service Order |
E13368
|
entity |
| Predicate | orderOfWearInUK |
P16982
|
FINISHED |
| Object | below Conspicuous Gallantry Cross |
—
|
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: below Conspicuous Gallantry Cross | Statement: [Distinguished Service Order, orderOfWearInUK, below Conspicuous Gallantry Cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderOfWearInUK Context triple: [Distinguished Service Order, orderOfWearInUK, below Conspicuous Gallantry Cross]
-
A.
wornFor
Indicates that an item is worn for a particular purpose, function, or occasion.
-
B.
wearingClass
Indicates that one entity is wearing or dressed in an item belonging to a particular class or category of clothing or accessories.
-
C.
wears
Indicates that one entity is dressed in, or has on its body, a particular item such as clothing or accessories.
-
D.
wornAs
Indicates that one entity is used or put on as clothing, an accessory, or a wearable item by another entity.
-
E.
wearingMethod
Indicates the manner or method by which something is worn or put on.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0ad379c81909003d35c63822780 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d221d38819083c0adda81f59b07 |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a49dc0e6a08190b81d82a6f2571c41 |
completed | March 1, 2026, 8:12 p.m. |
Created at: March 1, 2026, 7:36 p.m.