Triple
T31690720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of California system transportation research network |
E808781
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transportation research consortium |
C4656
|
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 research consortium Context triple: [University of California system transportation research network, instanceOf, transportation research consortium]
-
A.
transportation research program
A transportation research program is an organized initiative that systematically studies and develops knowledge, technologies, and policies to improve the safety, efficiency, sustainability, and equity of transportation systems.
-
B.
transportation organization
chosen
A transportation organization is an entity that plans, manages, and operates systems or services that move people or goods from one location to another.
-
C.
transport sector
The transport sector encompasses all systems, services, and infrastructure involved in moving people and goods by road, rail, air, and water.
-
D.
public transport information system
A public transport information system is a software platform that collects, processes, and disseminates real-time and scheduled data about public transit services to passengers, operators, and other stakeholders.
-
E.
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.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:08 p.m.