Triple
T2652532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drug and Alcohol Clearinghouse |
E53932
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transportation safety information system |
C8739
|
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: transportation safety information system Context triple: [Drug and Alcohol Clearinghouse, instanceOf, transportation safety information system]
-
A.
transportation safety agency
A transportation safety agency is an organization responsible for regulating, monitoring, and enforcing safety standards across transportation systems to prevent accidents and protect the public.
-
B.
transportation database
chosen
A transportation database is a structured collection of data that stores, organizes, and manages information related to transportation systems, such as routes, vehicles, schedules, and passenger or cargo records, to support planning, operations, and analysis.
-
C.
public transit safety oversight agency
A public transit safety oversight agency is a governmental or quasi-governmental body responsible for setting, monitoring, and enforcing safety standards and practices across public transportation systems to protect passengers, workers, and the public.
-
D.
public transport ticketing system
A public transport ticketing system manages the purchase, validation, and tracking of fares and passes for passengers across various transit services.
-
E.
transportation standard
A transportation standard is an agreed-upon set of rules, specifications, and protocols that ensure compatibility, safety, and efficiency across transportation systems, vehicles, and infrastructure.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
Created at: March 6, 2026, 9:53 p.m.