Triple
T5604926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Transport Strategy for Scotland |
E147210
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transport policy framework |
C19343
|
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: transport policy framework Context triple: [National Transport Strategy for Scotland, instanceOf, transport policy framework]
-
A.
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.
-
B.
transport strategy
A transport strategy is a high-level plan that defines how people and goods will be moved efficiently, safely, sustainably, and cost-effectively within and between areas over a given time horizon.
-
C.
transport model
A transport model is a conceptual or mathematical representation used to simulate and analyze the movement of people, goods, or resources across a network or spatial system under various conditions and constraints.
-
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.
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.
- 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:39 p.m.