Triple
T24173810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beusselstraße |
E599219
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transport infrastructure in Berlin |
C31848
|
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 infrastructure in Berlin Context triple: [Beusselstraße, instanceOf, transport infrastructure in Berlin]
-
A.
S-Bahn Berlin infrastructure segment
An S-Bahn Berlin infrastructure segment represents a contiguous portion of the Berlin S-Bahn network’s physical and operational assets—such as tracks, stations, signaling, and power supply—treated as a single unit for planning, maintenance, and service management.
-
B.
Verkehrsbauwerk in Berlin
A "Verkehrsbauwerk in Berlin" is a transportation-related structure within the city of Berlin, such as bridges, tunnels, stations, or other built facilities that support and organize traffic flow.
-
C.
road in Berlin
chosen
A road in Berlin is a public thoroughfare within the city’s urban network that facilitates vehicular, bicycle, and pedestrian movement while integrating with Berlin’s historical layout, public transit, and zoning infrastructure.
-
D.
Berlin S-Bahn service
Berlin S-Bahn service is a rapid transit and suburban rail network that provides frequent, high-capacity train connections across Berlin and its surrounding metropolitan region.
-
E.
Berlin U-Bahn facility
A Berlin U-Bahn facility is any physical structure, station, depot, or related infrastructure element that supports the operation, maintenance, or use of Berlin’s underground rapid transit system.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 11:33 p.m.