Triple
T12266646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airman Battle Uniform |
E292362
|
entity |
| Predicate | wearerInsigniaPlacement |
P55523
|
FINISHED |
| Object | subdued cloth insignia |
—
|
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: subdued cloth insignia | Statement: [Airman Battle Uniform, wearerInsigniaPlacement, subdued cloth insignia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wearerInsigniaPlacement Context triple: [Airman Battle Uniform, wearerInsigniaPlacement, subdued cloth insignia]
-
A.
rankInsigniaWornOn
chosen
Indicates the physical location on a uniform or body where a rank insignia is displayed or attached.
-
B.
wearsInsigniaAt
Indicates that an entity is wearing or displaying a particular insignia at a specified location or point in time.
-
C.
hasInsigniaWornBy
Indicates that a particular insignia is worn by a specified entity (such as a person, group, or organization).
-
D.
wearerStatus
Indicates the condition or role of an entity in its capacity as a wearer of something (e.g., clothing, equipment, or an accessory).
-
E.
wearLocation
Indicates the typical body part or location on which an item is worn.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9380a5e78819086bd4dfe9a83d1f5 |
completed | April 10, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69d91c4a66cc819083ce6fcaf5042af6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.