Triple
T31704420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EMPAR radar |
E809140
|
entity |
| Predicate | supportsMissileSystem |
P116373
|
FINISHED |
| Object | Aster 15 |
E231484
|
NE 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: Aster 15 | Statement: [EMPAR radar, supportsMissileSystem, Aster 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMissileSystem Context triple: [EMPAR radar, supportsMissileSystem, Aster 15]
-
A.
usesMissileSystem
Indicates that one entity employs or operates a particular missile system as part of its capabilities or actions.
-
B.
hasMissileDetectionSystem
Indicates that an entity is equipped with a system capable of detecting missiles.
-
C.
compatibleMissile
chosen
Indicates that a missile can be correctly used with, mounted on, or launched by a given platform or launcher system.
-
D.
supportsMissionType
Indicates that one entity is capable of handling, enabling, or being compatible with a specified type of mission.
-
E.
opposingWeaponSystem
Indicates that one weapon system is designed, used, or configured to counter, neutralize, or operate in direct opposition to another weapon system.
- F. None of above.
Provenance (4 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2ed4ca909881908c141632a41cb6f9 |
completed | June 14, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:13 p.m.