Triple
T9631139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dams Raid 1943 |
E232804
|
entity |
| Predicate | RAFLosses |
P8356
|
FINISHED |
| Object | several aircraft shot down |
—
|
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: several aircraft shot down | Statement: [Dams Raid 1943, RAFLosses, several aircraft shot down]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RAFLosses Context triple: [Dams Raid 1943, RAFLosses, several aircraft shot down]
-
A.
usesLossFunction
Indicates that one entity employs a particular loss function as part of its optimization or learning process.
-
B.
lossType
Indicates the specific category or nature of a loss associated with an entity or event.
-
C.
regionOfLoss
Indicates the anatomical or spatial area where a loss, damage, or deficit occurs or is localized.
-
D.
losses
chosen
Indicates that an entity experiences a decrease in value, quantity, or advantage as a result of some event or comparison.
-
E.
causedLossOf
Indicates that one entity brought about or was responsible for another entity experiencing a loss.
- 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_69ca848940cc8190b97cec654cb3bb4a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b2621408190bfe2ea5a05359ee0 |
completed | April 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:11 p.m.