Triple
T35519925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bachem-Werke |
E1026523
|
entity |
| Predicate | aircraftArmament |
P183197
|
FINISHED |
| Object | air-to-air rockets (Ba 349) |
—
|
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 rockets (Ba 349) | Statement: [Bachem-Werke, aircraftArmament, air-to-air rockets (Ba 349)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftArmament Context triple: [Bachem-Werke, aircraftArmament, air-to-air rockets (Ba 349)]
-
A.
aircraftDefensiveArmament
Indicates that an aircraft is equipped with weapons or systems specifically intended for its own defense against attacks.
-
B.
referredAircraftArmament
Indicates that one aircraft’s armament is being referenced or pointed to in relation to another entity or context.
-
C.
weaponsBay
Indicates that one entity serves as the weapons bay (storage or housing area for weapons) of another entity.
-
D.
gunDeckArmament
Indicates the type or configuration of weapons mounted on a ship’s gun deck.
-
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. chosen
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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79a53ccc481908421ae16e69aa8a4 |
completed | May 3, 2026, 6:56 p.m. |
Created at: May 3, 2026, 4:04 p.m.