Triple
T53325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operational Camouflage Pattern |
E1049
|
entity |
| Predicate | optimizedFor |
P98
|
FINISHED |
| Object | near-infrared performance |
—
|
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: near-infrared performance | Statement: [Operational Camouflage Pattern, optimizedFor, near-infrared performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: optimizedFor Context triple: [Operational Camouflage Pattern, optimizedFor, near-infrared performance]
-
A.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
-
B.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
-
D.
envisionedAs
Indicates that one entity is mentally pictured, imagined, or conceived in terms of another entity or role.
-
E.
recognizedFor
Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24c709c248190bcd442c8d508e48c |
completed | Feb. 28, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69a24ac3c8dc819099849023bdaa35a9 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.