Triple
T26990510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Navy uniforms |
E679849
|
entity |
| Predicate | hasHeadgearType |
P31655
|
FINISHED |
| Object | combination cover |
—
|
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: combination cover | Statement: [U.S. Navy uniforms, hasHeadgearType, combination cover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeadgearType Context triple: [U.S. Navy uniforms, hasHeadgearType, combination cover]
-
A.
hasHeadbandType
Indicates that an entity is associated with a specific type or style of headband.
-
B.
authorizedHeadgear
Indicates that a particular item of headgear is officially permitted or approved for use in a given context or by a specific authority.
-
C.
associatedWithHeadgear
chosen
Indicates a relationship where an entity is connected or related to a particular item of headgear, such as by wearing, using, or being characterized by it.
-
D.
helmetNumberStatus
Indicates the status or condition associated with an entity’s helmet number (e.g., whether it is assigned, valid, active, or otherwise designated).
-
E.
helmetType
Indicates the specific category or style of helmet associated with an entity.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 27, 2026, 6:51 a.m.