Triple
T21349960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rayners Lane station |
E526447
|
entity |
| Predicate | isSubsurfaceStation |
P45858
|
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: [Rayners Lane station, isSubsurfaceStation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubsurfaceStation Context triple: [Rayners Lane station, isSubsurfaceStation, yes]
-
A.
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.
-
B.
hasSubsurfacePlatforms
chosen
Indicates that an entity includes or is equipped with platforms located below the surface or underground.
-
C.
hasUndergroundDepth
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
D.
subsurfaceSamplingDevice
Indicates a device is used to collect or sample materials from beneath a surface, such as soil, rock, or sediment layers.
-
E.
isInCavernSystem
Indicates that one entity is located within or forms part of an interconnected network of underground caverns associated with another entity.
- 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8ad30512081909012ce318fa67679 |
completed | April 22, 2026, 11:12 a.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:03 p.m.