Triple
T16652476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GBU-10 Paveway II |
E404639
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | GBU-10F/B |
E1226609
|
NE 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: GBU-10F/B | Statement: [GBU-10 Paveway II, hasVariant, GBU-10F/B]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GBU-10F/B Context triple: [GBU-10 Paveway II, hasVariant, GBU-10F/B]
-
A.
GBU-10E/B
chosen
The GBU-10E/B is a specific variant of the U.S. 2,000-pound laser-guided Paveway II bomb, designed for precision strikes against high-value targets.
-
B.
GBU-15
The GBU-15 is a U.S. air-launched, precision-guided glide bomb that uses electro-optical or infrared guidance for standoff attacks on ground targets.
-
C.
GBU-51
The GBU-51 is a precision-guided Joint Direct Attack Munition (JDAM) variant designed to deliver accurate air-to-surface strikes using GPS/INS guidance.
-
D.
GBU-54
The GBU-54 is a U.S. precision-guided bomb that combines GPS/INS guidance with a laser seeker to accurately strike both stationary and moving targets.
-
E.
GBU-28
The GBU-28 is a U.S. laser-guided, bunker-buster bomb designed to penetrate deeply buried and hardened targets.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bf7ae7c81908b6807acd8f1669b |
completed | April 18, 2026, 12:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a008a2f1da48190a1a01dbe25f8f0e9 |
completed | May 10, 2026, 1:37 p.m. |
Created at: April 10, 2026, 5:18 a.m.