Triple
T33504215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Traffic Control |
E858071
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | safety-critical system |
C59195
|
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: safety-critical system Context triple: [Air Traffic Control, instanceOf, safety-critical system]
-
A.
safety-critical system architecture
A safety-critical system architecture is a structured design of hardware and software components, interfaces, and safeguards that ensures essential functions operate reliably and fail-safe under all specified conditions to prevent harm to people, property, or the environment.
-
B.
public safety system
A public safety system is an integrated framework of technologies, policies, and coordinated services designed to prevent, detect, respond to, and recover from threats or emergencies affecting the well-being of a community.
-
C.
spacecraft safety system
A spacecraft safety system is an integrated set of hardware, software, and procedural controls designed to detect, prevent, and mitigate hazards to protect the vehicle, crew, payload, and mission throughout all phases of spaceflight.
-
D.
automotive safety system
An automotive safety system is an integrated set of components and technologies designed to prevent accidents or reduce injury and damage when collisions occur.
-
E.
cybersecurity system
A cybersecurity system is an integrated set of tools, policies, and processes designed to protect digital assets, networks, and data from unauthorized access, attacks, and damage.
- F. None of above. chosen
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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:38 a.m.