Triple
T34602259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transport for London area |
E888498
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative transport region |
C42171
|
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: administrative transport region Context triple: [Transport for London area, instanceOf, administrative transport region]
-
A.
public transport region
chosen
A public transport region is a defined geographic area within which public transportation services are planned, coordinated, and managed as an integrated network.
-
B.
administrative territorial unit code
An administrative territorial unit code is a standardized identifier assigned to a specific geographic or political subdivision within a country for the purposes of administration, statistics, and governance.
-
C.
regional administrative branch
A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
-
D.
regional transport office code
A regional transport office code is a standardized alphanumeric identifier assigned to a specific geographic transport authority area, used to uniquely mark and track vehicle registrations and related administrative records.
-
E.
administrative territorial entity
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
- 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:03 a.m.