Triple
T25842267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark 48 torpedo |
E650967
|
entity |
| Predicate | warheadFiller |
P76590
|
FINISHED |
| Object | PBXN-103 (later variants) |
—
|
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: PBXN-103 (later variants) | Statement: [Mark 48 torpedo, warheadFiller, PBXN-103 (later variants)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warheadFiller Context triple: [Mark 48 torpedo, warheadFiller, PBXN-103 (later variants)]
-
A.
warheadFilling
chosen
Indicates that one entity serves as the explosive filling or payload contained within a warhead entity.
-
B.
warheadFuzing
Indicates the method or mechanism by which a warhead is triggered or detonated in relation to its target or flight conditions.
-
C.
warheadName
Indicates the specific name or designation assigned to a warhead associated with an entity or system.
-
D.
warheadPlacement
Indicates the positioning or allocation of a warhead onto or within a specific delivery system, target, or location.
-
E.
warheadEffect
Indicates the type or nature of impact, damage, or outcome produced when a warhead is used or detonated.
- 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_69e7ab38086081908f3a8e7e0c6efd83 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f601f9c4c48190bfc072f720c86868 |
completed | May 2, 2026, 1:54 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:50 a.m.