Triple
T14165053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M549A1 RAP projectile |
E351050
|
entity |
| Predicate | fuzingOptions |
P27067
|
FINISHED |
| Object | point-detonating 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: point-detonating fuze | Statement: [M549A1 RAP projectile, fuzingOptions, point-detonating fuze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuzingOptions Context triple: [M549A1 RAP projectile, fuzingOptions, point-detonating fuze]
-
A.
fuseType
Indicates the specific kind or category of fuse associated with or used in relation to an entity.
-
B.
fireModes
Indicates the different ways or settings in which a weapon or device can be fired or operated.
-
C.
fusionReactionType
Indicates the specific kind or category of nuclear fusion process that relates two or more participating entities.
-
D.
warheadFuzing
chosen
Indicates the method or mechanism by which a warhead is triggered or detonated in relation to its target or flight conditions.
-
E.
optionedBy
Indicates that the rights to develop, produce, or exploit something (such as a work, property, or asset) have been contractually secured by a particular party.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b207cc8190b85b1ff0910b54da |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:59 a.m.