Triple
T2117956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glasgow Queen Street railway station |
E43850
|
entity |
| Predicate | hasUpperLevelPlatforms |
P843
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Glasgow Queen Street railway station, hasUpperLevelPlatforms, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpperLevelPlatforms Context triple: [Glasgow Queen Street railway station, hasUpperLevelPlatforms, 7]
-
A.
hasSidePlatforms
Indicates that something is equipped with platforms located on its sides, typically for access, support, or operation.
-
B.
hasNumberOfPlatforms
chosen
Indicates the relationship that specifies how many platforms are associated with a given entity.
-
C.
hasIslandPlatforms
Indicates that the subject has one or more island-style platforms, typically positioned between tracks and accessible from both sides.
-
D.
hasShelteredPlatforms
Indicates that the subject provides or includes platforms that are covered or protected from the elements.
-
E.
hasTerminatingPlatforms
Indicates that the subject location or facility includes platforms where rail or transit services begin or end their routes, rather than passing through.
- 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_69a88717cfe48190b7ecdd68c824848a |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb2f6f608190937889bb393fe7c6 |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bbf9d881909d223b0cab7cab18 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.