Triple
T38689975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FuG 230 Straßburg |
E949233
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military electronic equipment |
C2498
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: military electronic equipment Context triple: [FuG 230 Straßburg, instanceOf, military electronic equipment]
-
A.
military equipment
Military equipment comprises the specialized weapons, vehicles, protective gear, communication systems, and support tools designed, produced, and used by armed forces to conduct and support combat and defense operations.
-
B.
military technology
Military technology encompasses the specialized tools, systems, and innovations developed and used by armed forces to enhance their capabilities in defense, offense, intelligence, and logistics.
-
C.
military radar system
chosen
A military radar system is an integrated sensor platform that emits and receives electromagnetic signals to detect, track, and classify airborne, maritime, or ground targets for surveillance, targeting, and defense operations.
-
D.
military cryptographic device
A military cryptographic device is a secure hardware system used by armed forces to encrypt, decrypt, and protect sensitive communications and data against unauthorized access and interception.
-
E.
Soviet military equipment
Soviet military equipment encompasses the weapons, vehicles, and support systems designed and produced by the Soviet Union to equip its armed forces, characterized by rugged construction, mass production, and doctrinal emphasis on large-scale, combined-arms warfare.
- F. None of above.
Provenance (1 batch)
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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:33 p.m.