Triple
T28719861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DAAFAR |
E730061
|
entity |
| Predicate | usedWeaponSystemType |
P89527
|
FINISHED |
| Object | surface-to-air missile system |
—
|
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: surface-to-air missile system | Statement: [DAAFAR, usedWeaponSystemType, surface-to-air missile system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedWeaponSystemType Context triple: [DAAFAR, usedWeaponSystemType, surface-to-air missile system]
-
A.
usedWeapon
Indicates that an entity employed a specific weapon as the means or tool to carry out an action or event.
-
B.
usedOnWeaponSystem
Indicates that something (such as a component, technology, or material) is employed as part of, or in conjunction with, a weapon system.
-
C.
weaponSystemType
chosen
Indicates the specific category or kind of weapon system associated with an entity.
-
D.
hasWeaponType
Indicates that an entity is associated with or equipped with a specific type or category of weapon.
-
E.
weaponSystemAssociatedWith
Indicates that one entity is functionally or organizationally connected to a particular weapon system, such as by using, supporting, or being part of that system.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 5:52 a.m.