Triple
T269599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Camouflage Pattern |
E5600
|
entity |
| Predicate | fullyReplacedInPracticeBy |
P101
|
FINISHED |
| Object | late 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: late 2010s | Statement: [Universal Camouflage Pattern, fullyReplacedInPracticeBy, late 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullyReplacedInPracticeBy Context triple: [Universal Camouflage Pattern, fullyReplacedInPracticeBy, late 2010s]
-
A.
usedInsteadOf
Indicates that one entity is employed or chosen as a substitute or replacement for another entity.
-
B.
replacedSystemUsedUntil
Indicates that one system was used up until it was replaced by another system.
-
C.
wasSupersededBy
chosen
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
D.
isAlternativeTo
Indicates that one entity can serve as a substitute or different option in place of another.
-
E.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
- 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_69a25853594c8190b05ec3a586ec88bf |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25db00ed48190be6f598807265356 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b70d99c819085d8381a313a2a34 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.