Triple
T32185660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airman First Class (USSF enlisted rank) |
E822101
|
entity |
| Predicate | hasRankInsigniaShape |
P181454
|
FINISHED |
| Object | chevron-style 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: chevron-style insignia | Statement: [Airman First Class (USSF enlisted rank), hasRankInsigniaShape, chevron-style insignia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankInsigniaShape Context triple: [Airman First Class (USSF enlisted rank), hasRankInsigniaShape, chevron-style insignia]
-
A.
rankInsigniaShape
chosen
Indicates the geometric form or outline that characterizes a rank insignia in a hierarchy.
-
B.
rankInsigniaWornOn
Indicates the physical location on a uniform or body where a rank insignia is displayed or attached.
-
C.
isHighestRankInsigniaOf
Indicates that one insignia represents the highest possible rank within a specified organization, hierarchy, or context.
-
D.
hasTypeOfInsignia
Indicates that an entity bears or is associated with a specific kind or category of insignia.
-
E.
hasHeraldicShieldShape
Indicates that an entity’s heraldic shield is characterized by a specific geometric or stylistic shape.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 1, 2026, 12:35 a.m.