Triple
T19375300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transport for London river services framework |
E484651
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transport regulatory framework |
C11529
|
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: public transport regulatory framework Context triple: [Transport for London river services framework, instanceOf, public transport regulatory framework]
-
A.
transport policy framework
A transport policy framework is a structured set of principles, goals, and regulatory tools that guide the planning, funding, operation, and governance of transportation systems to achieve economic, social, and environmental objectives.
-
B.
transportation safety law
Transportation safety law is the body of legal rules and regulations designed to prevent accidents and injuries in all modes of transport by setting safety standards, enforcing compliance, and assigning liability for violations.
-
C.
regulatory framework
chosen
A regulatory framework is a structured set of rules, guidelines, and enforcement mechanisms established by authorities to govern behaviors, processes, and standards within a specific domain.
-
D.
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.
-
E.
transport policy body
A transport policy body is an organization or authority responsible for developing, coordinating, and overseeing regulations, strategies, and standards that govern transportation systems and services.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:35 p.m.