Triple
T2885336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Desert Camouflage Uniform |
E59490
|
entity |
| Predicate | replacedInMostRolesBy |
P40785
|
FINISHED |
| Object | digital camouflage uniforms |
—
|
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: digital camouflage uniforms | Statement: [Desert Camouflage Uniform, replacedInMostRolesBy, digital camouflage uniforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedInMostRolesBy Context triple: [Desert Camouflage Uniform, replacedInMostRolesBy, digital camouflage uniforms]
-
A.
partlyReplacedBy
chosen
Indicates that one entity has been superseded or substituted in part, but not entirely, by another entity.
-
B.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
C.
successorRole
Indicates that one role or position directly follows and replaces another in a sequence or organizational structure.
-
D.
alsoServedAs
Indicates that an entity held an additional role or position beyond the primary one already mentioned.
-
E.
usedInsteadOf
Indicates that one entity is employed or chosen as a substitute or replacement for another 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_69ab4ac739188190a112f42a5a69c951 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abe04476588190b0db0880e14c79b5 |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd15cbf08190bf7fea5ea516848a |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.