Triple
T24916917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Glasgow railway station |
E624013
|
entity |
| Predicate | directionFromGlasgowCentral |
P71564
|
FINISHED |
| Object | west |
—
|
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: west | Statement: [Port Glasgow railway station, directionFromGlasgowCentral, west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromGlasgowCentral Context triple: [Port Glasgow railway station, directionFromGlasgowCentral, west]
-
A.
directionFromGlasgow
chosen
Indicates the compass direction in which one entity is located relative to Glasgow.
-
B.
geographicDirectionFromEdinburgh
Indicates the geographic direction in which one place or entity is located relative to Edinburgh.
-
C.
distanceFromGlasgow
Indicates the spatial distance separating a given entity or location from Glasgow.
-
D.
followingStationOnNorthClydeLineTowardsGlasgow
Indicates that one station is the next station along the North Clyde railway line in the direction of travel towards Glasgow.
-
E.
directionFromCityCentre
Indicates the compass direction in which one location lies relative to the city centre.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:28 a.m.