Triple
T17176952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Road Transport Executive |
E416884
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | division of the British Transport Commission |
C38635
|
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: division of the British Transport Commission Context triple: [Road Transport Executive, instanceOf, division of the British Transport Commission]
-
A.
region of British Railways
A region of British Railways is a large administrative and operational division of the national rail network, responsible for managing railway services, infrastructure, and staff within a defined geographic area of Great Britain.
-
B.
Inland Transport Committee
The Inland Transport Committee is a policy-making body that develops and coordinates international regulations, standards, and best practices to promote safe, efficient, and sustainable inland transport systems.
-
C.
former British Rail sector
A former British Rail sector is an organizational division that once managed specific types of rail services or geographic areas within the state-owned British Rail system before its restructuring and privatization.
-
D.
British Railways policy document
A British Railways policy document is an official written directive issued by British Railways that defines rules, procedures, and standards governing its operations, staff conduct, and strategic decisions.
-
E.
London Underground precursor
A London Underground precursor is any early urban rail or transport system, proposal, or technological development that directly influenced or led to the creation of the London Underground.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:37 a.m.