Triple
T1785416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | surface-based launcher (NASAMS) |
E39379
|
entity |
| Predicate | munitionType |
P6074
|
FINISHED |
| Object | active radar homing missile |
—
|
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: active radar homing missile | Statement: [surface-based launcher (NASAMS), munitionType, active radar homing missile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: munitionType Context triple: [surface-based launcher (NASAMS), munitionType, active radar homing missile]
-
A.
ammunitionType
chosen
Indicates the specific kind or category of ammunition associated with or used by an entity.
-
B.
ammunitionCapacity
Indicates the maximum amount of ammunition that something (typically a weapon or container) is designed to hold at one time.
-
C.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
-
D.
typicalOrdnance
Indicates that something is a standard or commonly used type of weaponry or munitions associated with a given entity or context.
-
E.
gunType
Indicates the specific category or kind of gun associated with an entity.
- 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab75457e54819096b8c6ae8c65550c |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61d165688190924962a98e07ff69 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.