Triple
T34283954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Südbahnhof (Frankfurt am Main) |
E879678
|
entity |
| Predicate | hasSurfacePlatforms |
P107995
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Südbahnhof (Frankfurt am Main), hasSurfacePlatforms, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfacePlatforms Context triple: [Südbahnhof (Frankfurt am Main), hasSurfacePlatforms, yes]
-
A.
hasSubSurfacePlatformsFor
Indicates that one entity provides or contains subsurface platforms intended to support, serve, or be used by another entity.
-
B.
hasNumberOfPlatforms
Indicates the relationship that specifies how many platforms are associated with a given entity.
-
C.
hadPlatforms
Indicates that something was equipped with or featured one or more platforms.
-
D.
hasSidePlatforms
Indicates that something is equipped with platforms located on its sides, typically for access, support, or operation.
-
E.
hasAtGradePlatforms
chosen
Indicates that the subject has platforms located at the same level as the surrounding ground or track (i.e., not elevated or underground).
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff8ba3f8248190bbdf8e7ec2b35093 |
completed | May 9, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69ff8b41ba988190a7332e8317d10f09 |
completed | May 9, 2026, 7:30 p.m. |
Created at: May 1, 2026, 1:57 a.m.