Triple
T29821713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Woodland |
E757260
|
entity |
| Predicate | usedInClothingType |
P15063
|
FINISHED |
| Object | battle dress uniform |
—
|
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: battle dress uniform | Statement: [U.S. Woodland, usedInClothingType, battle dress uniform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInClothingType Context triple: [U.S. Woodland, usedInClothingType, battle dress uniform]
-
A.
alsoWornIn
Indicates that an item of clothing or accessory is additionally worn in another context, location, or time beyond the primary one mentioned.
-
B.
clothingPurpose
Indicates the functional role or intended use that a particular item of clothing serves (e.g., protection, fashion, uniform, sport).
-
C.
garmentType
chosen
Indicates the specific kind or category of garment associated with an entity.
-
D.
usesDressing
Indicates that one entity applies or employs a particular dressing (such as a sauce, covering, or treatment) in relation to another entity or context.
-
E.
typicallyWornWith
Indicates that one item of clothing or accessory is commonly or customarily worn together with another.
- 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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 29, 2026, 5:29 p.m.