Triple
T34415569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verkehrsgemeinschaft Westmecklenburg |
E883394
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional transport association |
C64277
|
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: regional transport association Context triple: [Verkehrsgemeinschaft Westmecklenburg, instanceOf, regional transport association]
-
A.
Regional Transport Office
A Regional Transport Office is a government agency responsible for vehicle registration, driver licensing, enforcement of transport regulations, and maintenance of regional motor vehicle records.
-
B.
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.
-
C.
rail transport district
A rail transport district is a designated geographic area organized and managed to provide, coordinate, and regulate rail-based transportation services and infrastructure within its boundaries.
-
D.
regional transport plan
A regional transport plan is a strategic framework that outlines long-term goals, policies, and coordinated investments for transportation systems across a defined geographic region.
-
E.
transport infrastructure operator
A transport infrastructure operator is an entity responsible for managing, maintaining, and regulating transportation networks and facilities such as roads, railways, ports, or airports to ensure safe and efficient movement of people and goods.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:59 a.m.