Triple
T3480976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taurus KEPD 350 |
E73488
|
entity |
| Predicate | warheadFunction |
P46849
|
FINISHED |
| Object | penetration and blast-fragmentation |
—
|
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: penetration and blast-fragmentation | Statement: [Taurus KEPD 350, warheadFunction, penetration and blast-fragmentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warheadFunction Context triple: [Taurus KEPD 350, warheadFunction, penetration and blast-fragmentation]
-
A.
warheadEffect
chosen
Indicates the type or nature of impact, damage, or outcome produced when a warhead is used or detonated.
-
B.
warheadFuzing
Indicates the method or mechanism by which a warhead is triggered or detonated in relation to its target or flight conditions.
-
C.
warheadMass
Indicates the mass or weight of a warhead associated with an entity or system.
-
D.
warheadOwnership
Indicates that one entity possesses or controls a particular warhead as its owner.
-
E.
warheadDesignOrigin
Indicates the original source or provenance of a warhead’s design in relation to the warhead itself.
- 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_69ad85b3c9b08190857cae74c7f36da9 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb75850c8190ad02cf2bde8be8a7 |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae0935ac8190bfa8a8bd3dcd3301 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.