Triple
T34197635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Desert DPM combat dress |
E877284
|
entity |
| Predicate | largelyPhasedOutBy |
P162723
|
FINISHED |
| Object | 2010s |
—
|
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: 2010s | Statement: [Desert DPM combat dress, largelyPhasedOutBy, 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: largelyPhasedOutBy Context triple: [Desert DPM combat dress, largelyPhasedOutBy, 2010s]
-
A.
graduallyPhasedOutIn
chosen
Indicates that something is discontinued or removed in a particular context or period through a slow, step-by-step process rather than all at once.
-
B.
discontinuedInFavorOf
Indicates that one thing has been stopped, ended, or phased out specifically so it can be replaced by another preferred alternative.
-
C.
decommissionedBy
Indicates that an entity was formally taken out of service or use by a specific agent or authority.
-
D.
partlyReplacedBy
Indicates that one entity has been superseded or substituted in part, but not entirely, by another entity.
-
E.
eraOfObsolescence
Indicates the time period during which something becomes outdated, no longer useful, or superseded by newer alternatives.
- 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7102a2d808190bc0232816d294d97 |
completed | May 3, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.