Triple
T13188837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TOW missile launcher |
E313928
|
entity |
| Predicate | warheadCompatibility |
P61965
|
FINISHED |
| Object | high-explosive anti-tank warhead |
—
|
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-explosive anti-tank warhead | Statement: [TOW missile launcher, warheadCompatibility, high-explosive anti-tank warhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warheadCompatibility Context triple: [TOW missile launcher, warheadCompatibility, high-explosive anti-tank warhead]
-
A.
warheadTypes
chosen
Indicates the types or categories of warheads associated with a given weapon or delivery system.
-
B.
warheadName
Indicates the specific name or designation assigned to a warhead associated with an entity or system.
-
C.
warheadOwnership
Indicates that one entity possesses or controls a particular warhead as its owner.
-
D.
warheadMass
Indicates the mass or weight of a warhead associated with an entity or system.
-
E.
warheadDeliveryMethod
Indicates the method or mechanism by which a warhead is transported, deployed, or delivered to its target.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:15 p.m.