Triple
T22008249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B61 nuclear bomb |
E543505
|
entity |
| Predicate | B61-12Features |
P146256
|
FINISHED |
| Object | precision guidance tail kit |
—
|
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: precision guidance tail kit | Statement: [B61 nuclear bomb, B61-12Features, precision guidance tail kit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: B61-12Features Context triple: [B61 nuclear bomb, B61-12Features, precision guidance tail kit]
-
A.
B-18BFeature
Indicates a relationship where something possesses or is characterized by a specific B-18B feature.
-
B.
bombType
Indicates the specific kind or category of bomb associated with an event, object, or action.
-
C.
nuclearExplosiveType
Indicates the specific category or kind of nuclear explosive device associated with an entity or event.
-
D.
notableMissile
Indicates that the subject is a missile distinguished by particular significance, prominence, or noteworthiness (e.g., historical impact, technological importance, or public attention).
-
E.
nuclearWarheadCarrier
Indicates that an entity is designed or used to carry, transport, or deliver nuclear warheads.
- F. None of above. chosen
Provenance (4 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127a2aebc8190951ee0bf9fd8e16d |
completed | April 28, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:21 p.m.