Triple
T8141524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Studio entertainment |
E190108
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | in-flight entertainment system |
C14046
|
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: in-flight entertainment system Context triple: [Delta Studio entertainment, instanceOf, in-flight entertainment system]
-
A.
avionics system
chosen
An avionics system is an integrated collection of electronic hardware and software on an aircraft that manages navigation, communication, monitoring, and control functions to ensure safe and efficient flight operations.
-
B.
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.
-
C.
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.
-
D.
media system
A media system is an integrated framework of technologies, institutions, content, and audiences that produces, distributes, and regulates information and entertainment within a society.
-
E.
cinema apparatus
A cinema apparatus is the integrated system of technologies, practices, and viewing conditions that together produce and structure the experience of watching films.
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:36 p.m.