Triple
T31949238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RP-9 radar |
E815734
|
entity |
| Predicate | guidesWeaponSystem |
P157462
|
FINISHED |
| Object | air-to-air missiles |
—
|
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: air-to-air missiles | Statement: [RP-9 radar, guidesWeaponSystem, air-to-air missiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guidesWeaponSystem Context triple: [RP-9 radar, guidesWeaponSystem, air-to-air missiles]
-
A.
guidesWeapon
chosen
Indicates that one entity directs or controls the operation or movement of a weapon associated with another entity.
-
B.
weaponSystemType
Indicates the specific category or kind of weapon system associated with an entity.
-
C.
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.
-
D.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
E.
introducedWeaponSystem
Indicates that an entity caused a new weapon system to be brought into use or formally adopted.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:07 a.m.