Triple
T30918622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Odyssey Lightning |
E787654
|
entity |
| Predicate | numberOfAirstrikes |
P72128
|
FINISHED |
| Object | over 400 airstrikes |
—
|
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: over 400 airstrikes | Statement: [Operation Odyssey Lightning, numberOfAirstrikes, over 400 airstrikes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfAirstrikes Context triple: [Operation Odyssey Lightning, numberOfAirstrikes, over 400 airstrikes]
-
A.
airStrikes
chosen
Indicates that one party conducts aerial attacks, typically using aircraft or drones, against a target or opposing party.
-
B.
numberOfMissilesLaunched
Indicates the total count of missiles that have been launched in a given context or event.
-
C.
numberOfCoordinatedAttacks
Indicates the total count of coordinated attacks carried out or associated with the given entity or event.
-
D.
numberOfPeopleInjuredInBombings
Indicates the count of individuals who were injured as a result of bombing incidents.
-
E.
numberOfExplosions
Indicates the count of distinct explosion events associated with an entity or situation.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00b3d2e0c88190a8bf49576e654f64 |
completed | May 10, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_6a00b376f4e48190a6676779fe02ea9f |
completed | May 10, 2026, 4:33 p.m. |
Created at: April 29, 2026, 8:51 p.m.