Triple
T14282912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eddie |
E354095
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | shipboard computer |
C1870
|
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: shipboard computer Context triple: [Eddie, instanceOf, shipboard computer]
-
A.
spacecraft onboard computer
A spacecraft onboard computer is a specialized, radiation-hardened computing system that autonomously manages spacecraft functions, navigation, communication, and data handling in the harsh environment of space.
-
B.
naval combat system component
chosen
A naval combat system component is an individual hardware or software element—such as a sensor, weapon, processor, or communication module—that contributes specific functionality to the detection, tracking, engagement, or control capabilities of an integrated maritime warfare system.
-
C.
attitude control computer
An attitude control computer is an onboard system that calculates and commands the necessary control actions to orient and stabilize a vehicle, such as a spacecraft or aircraft, in three-dimensional space.
-
D.
naval arsenal
A naval arsenal is a specialized military facility where warships are built, repaired, equipped, and supplied with weapons, ammunition, and other naval stores.
-
E.
integrated avionics suite
An integrated avionics suite is a cohesive collection of aircraft electronic systems—such as navigation, communication, flight control, and monitoring—designed to work together through shared hardware, software, and data networks to enhance safety, efficiency, and pilot situational awareness.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:10 a.m.