Triple
T34197613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Desert DPM combat dress |
E877284
|
entity |
| Predicate | inServiceDuringConflict |
P176299
|
FINISHED |
| Object | Gulf War |
—
|
NE NERFINISHED |
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: Gulf War | Statement: [Desert DPM combat dress, inServiceDuringConflict, Gulf War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inServiceDuringConflict Context triple: [Desert DPM combat dress, inServiceDuringConflict, Gulf War]
-
A.
implementedDuringConflict
Indicates that an action, policy, or measure was carried out while an active conflict or war was ongoing.
-
B.
allyInConflict
Indicates that one entity supports and cooperates with another entity as an ally within the context of a specific conflict or dispute.
-
C.
servedConflict
Indicates that an entity participated in or rendered service during a specific conflict, war, or military engagement.
-
D.
usedByDuringConflict
chosen
Indicates that one entity made practical use of another entity specifically in the context of a particular conflict or war.
-
E.
inService
Indicates that an entity is currently active, operational, or available for use in its intended role or function.
- 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.