Triple
T24112343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heidelberger Platz |
E597410
|
entity |
| Predicate | sBahnStationOpened |
P155103
|
FINISHED |
| Object | early 20th century |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: early 20th century | Statement: [Heidelberger Platz, sBahnStationOpened, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sBahnStationOpened Context triple: [Heidelberger Platz, sBahnStationOpened, early 20th century]
-
A.
busStationOpened
Indicates that a bus station began operating or was officially opened at a specific time or event.
-
B.
hasUBahnService
Indicates that a location or facility is served by, or has access to, an underground metro (U-Bahn) transit line.
-
C.
hasRailwayStationOn
Indicates that a railway station is located on or serves a particular railway line, route, or network segment.
-
D.
otherRailwayStation
Indicates a relationship where one railway station is associated with another as a distinct but related station, such as an alternative, nearby, or counterpart station.
-
E.
urbanRailHubFor
Indicates that a location functions as a central node or interchange point within an urban rail network for a given area or set of lines.
- F. None of above. chosen
Provenance (4 batches)
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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de1bd81c8190a44f07487d2ba176 |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17b58012c81909106b332db399023 |
completed | April 29, 2026, 3:30 a.m. |
Created at: April 17, 2026, 11:03 p.m.