Triple
T9784979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senior Airman (USSF enlisted rank) |
E237470
|
entity |
| Predicate | hasRankInsigniaColorScheme |
P29272
|
FINISHED |
| Object | USSF-specific color and design |
—
|
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: USSF-specific color and design | Statement: [Senior Airman (USSF enlisted rank), hasRankInsigniaColorScheme, USSF-specific color and design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankInsigniaColorScheme Context triple: [Senior Airman (USSF enlisted rank), hasRankInsigniaColorScheme, USSF-specific color and design]
-
A.
hasEmblemColor
Indicates that an emblem possesses or is characterized by a specific color.
-
B.
hasTypeOfInsignia
Indicates that an entity bears or is associated with a specific kind or category of insignia.
-
C.
rankInsigniaWornOn
Indicates the physical location on a uniform or body where a rank insignia is displayed or attached.
-
D.
hasColourScheme
chosen
Indicates that an entity is associated with a particular set or pattern of colors used in its design or appearance.
-
E.
corpsColour
Indicates the specific color associated with a military corps or unit.
- 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_69ca84da927881909bda80caecad6010 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda1b8b0a481909d9f7a25881d53be |
completed | April 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69cd03d77c6c81909b675955bf113320 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:27 p.m.