Triple
T19114050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tropical Blue uniform |
E467860
|
entity |
| Predicate | wornInLieuOf |
P6280
|
FINISHED |
| Object | Service Dress Blue 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: Service Dress Blue uniform | Statement: [Tropical Blue uniform, wornInLieuOf, Service Dress Blue uniform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wornInLieuOf Context triple: [Tropical Blue uniform, wornInLieuOf, Service Dress Blue uniform]
-
A.
wornAs
Indicates that one entity is used or put on as clothing, an accessory, or a wearable item by another entity.
-
B.
usedInsteadOf
chosen
Indicates that one entity is employed or chosen as a substitute or replacement for another entity.
-
C.
wornFor
Indicates that an item is worn for a particular purpose, function, or occasion.
-
D.
wornOver
Indicates that one item of clothing or accessory is positioned on top of and covering another item when worn.
-
E.
developedAsReplacementFor
Indicates that one entity was created or designed specifically to take the place of another entity, serving as its successor or substitute.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e39617408190b5134918f54f9c52 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.