Triple
T24932575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coburg railway station |
E623226
|
entity |
| Predicate | hasLiftAccessToPlatforms |
P35396
|
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: [Coburg railway station, hasLiftAccessToPlatforms, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiftAccessToPlatforms Context triple: [Coburg railway station, hasLiftAccessToPlatforms, yes]
-
A.
hasLiftOnlyAccessToPlatforms
Indicates that access to the platforms is provided exclusively via a lift (elevator), with no alternative means such as stairs or ramps.
-
B.
accessToPlatforms
Indicates that one entity is able to use, reach, or interact with certain platforms provided or controlled by another entity.
-
C.
hasLift
chosen
Indicates that one entity is equipped with, contains, or provides access to a lift (elevator).
-
D.
hasIslandPlatformAccess
Indicates that access is provided to or from an island platform, typically located between tracks and reachable by passengers.
-
E.
hasLevelAccessToPlatforms
Indicates that an entity is permitted to access certain platforms at a specified level or tier of authorization.
- 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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 5:30 a.m.