Triple
T53317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operational Camouflage Pattern |
E1049
|
entity |
| Predicate | initialFieldingBegan |
P3298
|
FINISHED |
| Object | 2015-07 |
—
|
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: 2015-07 | Statement: [Operational Camouflage Pattern, initialFieldingBegan, 2015-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialFieldingBegan Context triple: [Operational Camouflage Pattern, initialFieldingBegan, 2015-07]
-
A.
firstAwarded
Indicates the time or occasion when an award, honor, or recognition was given for the very first time.
-
B.
beganOfficialNumberingWith
Indicates that an entity started its formal or official numbering sequence with a specified initial number or identifier.
-
C.
hasBallpark
Indicates that an entity possesses, is associated with, or includes a specific ballpark as part of its attributes or facilities.
-
D.
firstCelebratedInYear
Indicates the year in which something (such as an event, holiday, or celebration) was first observed or celebrated.
-
E.
ballpark
Indicates an approximate or rough estimation of a value, rather than an exact or precise figure.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a24c6ff0588190b0fd864da9aa8569 |
completed | Feb. 28, 2026, 2:01 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.