Triple
T17132002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finstock railway station |
E415740
|
entity |
| Predicate | isLowUsageStation |
P126226
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Finstock railway station, isLowUsageStation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLowUsageStation Context triple: [Finstock railway station, isLowUsageStation, true]
-
A.
isLocalStation
Indicates that a station operates primarily within a limited local area or serves as a stop on a local (rather than regional or long-distance) service.
-
B.
hasLowerStation
Indicates that one entity occupies a lower rank, status, or position in a hierarchy relative to another entity.
-
C.
isSurfaceStation
Indicates that the station is located at or on the surface (e.g., ground level) rather than being underground, elevated, or otherwise non-surface.
-
D.
isLocalStationFor
Indicates that a station serves a specific local area or locality as its primary service point.
-
E.
isUrbanStation
Indicates that a station is located in an urban area or serves an urban environment.
- F. None of above. chosen
Provenance (4 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f02a9fbc81909d820d29417aa55c |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:36 a.m.