Triple
T10041813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RBS 56 BILL |
E205312
|
entity |
| Predicate | missileControl |
P86415
|
FINISHED |
| Object | command link via wire |
—
|
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: command link via wire | Statement: [RBS 56 BILL, missileControl, command link via wire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missileControl Context triple: [RBS 56 BILL, missileControl, command link via wire]
-
A.
missileLaunchCapability
Indicates that an entity has the ability or functionality to launch missiles.
-
B.
missileClass
Indicates the classification or type category assigned to a missile within a defined system or taxonomy.
-
C.
firingControl
chosen
Indicates a relationship where one entity directs, regulates, or initiates the firing or discharge action of another entity or system.
-
D.
fireControlSystem
Indicates a relationship where a system monitors, directs, and coordinates the detection, targeting, and firing of weapons or other actuators to control the application of force or energy.
-
E.
usesMissileSystem
Indicates that one entity employs or operates a particular missile system as part of its capabilities or actions.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcee48d8c8190af7c93b60f8ca7cb |
completed | April 2, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:55 p.m.