Triple
T30146930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Air Force peaked cap |
E766281
|
entity |
| Predicate | wornByRank |
P84687
|
FINISHED |
| Object | commissioned officers |
—
|
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: commissioned officers | Statement: [Royal Air Force peaked cap, wornByRank, commissioned officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wornByRank Context triple: [Royal Air Force peaked cap, wornByRank, commissioned officers]
-
A.
wearerRankRange
Indicates the range of ranks that an individual must fall within in order to be permitted or intended to wear a specified item.
-
B.
wearerRankCategory
Indicates the classification of the wearer's rank into a broader rank category (e.g., junior, senior, officer, etc.) within a ranking system.
-
C.
rankInsigniaWornOn
Indicates the physical location on a uniform or body where a rank insignia is displayed or attached.
-
D.
hasInsigniaWornBy
Indicates that a particular insignia is worn by a specified entity (such as a person, group, or organization).
-
E.
typicallyWornBy
chosen
Indicates that something (such as an item or garment) is most commonly or characteristically worn by a particular type of person or group.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67e8c266081909c00fbe8a1791436 |
completed | May 2, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:19 p.m.