Triple
T10787727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo Guidance Computer |
E254491
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | onboard computer |
C7917
|
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: onboard computer Context triple: [Apollo Guidance Computer, instanceOf, onboard computer]
-
A.
spacecraft onboard computer
chosen
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.
automotive computing platform
An automotive computing platform is an integrated hardware and software system within a vehicle that manages and coordinates functions such as infotainment, driver assistance, connectivity, and vehicle control in a secure and real-time manner.
-
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.
in-vehicle infotainment platform
An in-vehicle infotainment platform is an integrated hardware and software system that delivers multimedia, navigation, connectivity, and vehicle information services through the car’s user interfaces.
-
E.
digital instrument cluster
A digital instrument cluster is an electronic display system in a vehicle that replaces traditional analog gauges to present real-time driving information such as speed, RPM, fuel level, and warnings in a customizable, often graphical format.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:17 p.m.