Triple
T29618613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munich Ostbahnhof (S-Bahn underground platforms) |
E754931
|
entity |
| Predicate | positionOnCorridor |
P185429
|
FINISHED |
| Object | eastern end of Munich S-Bahn trunk line |
—
|
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: eastern end of Munich S-Bahn trunk line | Statement: [Munich Ostbahnhof (S-Bahn underground platforms), positionOnCorridor, eastern end of Munich S-Bahn trunk line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnCorridor Context triple: [Munich Ostbahnhof (S-Bahn underground platforms), positionOnCorridor, eastern end of Munich S-Bahn trunk line]
-
A.
focusesOnCorridor
Indicates that an action, attention, or process is directed specifically toward a corridor or passageway.
-
B.
locatedInTravelDirectionCorridor
Indicates that something is positioned within a corridor that lies along the direction of travel.
-
C.
onCorridorTo
chosen
Indicates that one location is directly connected to another via a corridor leading toward it.
-
D.
onCorridorBetween
Indicates that one entity is located along the corridor that lies between two other reference entities or areas.
-
E.
positionInWall
Indicates that one entity occupies a specific location or placement within a wall.
- F. None of above.
Provenance (3 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: April 28, 2026, 6:33 p.m.