Triple
T2770567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Provide Comfort |
E61444
|
entity |
| Predicate | usedMilitaryAsset |
P23907
|
FINISHED |
| Object | coalition air forces |
—
|
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: coalition air forces | Statement: [Operation Provide Comfort, usedMilitaryAsset, coalition air forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedMilitaryAsset Context triple: [Operation Provide Comfort, usedMilitaryAsset, coalition air forces]
-
A.
militaryUse
chosen
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
B.
postMilitaryUse
Indicates that an entity is used or repurposed after its original military function or service has ended.
-
C.
usedItem
Indicates that an entity has utilized or employed a particular item for some purpose.
-
D.
militaryCharacteristic
Indicates that one entity possesses a specific military-related attribute, quality, or feature in relation to another entity or context.
-
E.
usedWeapon
Indicates that an entity employed a specific weapon as the means or tool to carry out an action or event.
- 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_69ab4b7cd13481909174bca9809ed259 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdcfed608819080988e93df7bdf7c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.