Triple
T8294935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 20th Air Force |
E194190
|
entity |
| Predicate | typeOfBombing |
P21065
|
FINISHED |
| Object | High-altitude precision bombing |
—
|
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: High-altitude precision bombing | Statement: [20th Air Force, typeOfBombing, High-altitude precision bombing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBombing Context triple: [20th Air Force, typeOfBombing, High-altitude precision bombing]
-
A.
bombingMethod
chosen
Indicates the method or technique used to carry out a bombing.
-
B.
resultOfBombing
Indicates that something exists or occurs as a consequence or outcome of a bombing event.
-
C.
bombingName
Indicates that an entity is the name or designated title of a specific bombing event or bombing attack.
-
D.
bombingPlatform
Indicates that one entity serves as the platform or means from which another entity conducts or carries out a bombing.
-
E.
bombed
Indicates that one entity attacked another using explosive weapons, causing or intending to cause destruction or damage.
- 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_69ca82e50ebc81909aa7b260c76bd757 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7df5fff88190ac51a8d1c3eb2fe2 |
completed | March 31, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:52 p.m.