Triple
T6140293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helios 2 |
E136943
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military reconnaissance satellite |
C2826
|
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 reconnaissance satellite Context triple: [Helios 2, instanceOf, military reconnaissance satellite]
-
A.
satellite program
A satellite program is an organized initiative that designs, builds, launches, and operates satellites to achieve specific objectives such as communication, Earth observation, navigation, or scientific research.
-
B.
intelligence, surveillance and reconnaissance capability
Intelligence, surveillance and reconnaissance capability is the integrated ability to collect, process, analyze and disseminate information from multiple sources to provide timely situational awareness and support informed decision-making.
-
C.
military radar system
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.
spacecraft
chosen
A spacecraft is a vehicle or device designed to travel beyond Earth's atmosphere for purposes such as exploration, communication, research, or transportation.
-
E.
reconnaissance aircraft
A reconnaissance aircraft is a specialized military or intelligence-gathering airplane designed to observe, monitor, and collect information about enemy forces, terrain, or strategic targets using advanced sensors and surveillance equipment.
- 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_69c008a179388190a3b5a081bbf46d55 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:15 p.m.