Triple
T9388765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MM38 |
E225968
|
entity |
| Predicate | warheadDetonation |
P27067
|
FINISHED |
| Object | impact fuze |
—
|
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: impact fuze | Statement: [MM38, warheadDetonation, impact fuze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warheadDetonation Context triple: [MM38, warheadDetonation, impact fuze]
-
A.
warheadEffect
Indicates the type or nature of impact, damage, or outcome produced when a warhead is used or detonated.
-
B.
warheadFuzing
chosen
Indicates the method or mechanism by which a warhead is triggered or detonated in relation to its target or flight conditions.
-
C.
detonatedOver
Indicates that one entity caused an explosion or detonation to occur above or over another entity or location.
-
D.
usedAsWarheadFor
Indicates that something functions as the explosive or destructive payload component for a specified weapon or delivery system.
-
E.
detonationPosition
Indicates the specific location or coordinates at which a detonation occurs or is intended to occur.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50d6e5f081908102909cb4cbb649 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:45 p.m.