Triple
T25701766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lapford |
E644481
|
entity |
| Predicate | hasRailwayStationFeature |
P145777
|
FINISHED |
| Object | request stop |
—
|
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: request stop | Statement: [Lapford, hasRailwayStationFeature, request stop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailwayStationFeature Context triple: [Lapford, hasRailwayStationFeature, request stop]
-
A.
hasRailwayStation
Indicates that a place or location is served by, or contains, a railway station.
-
B.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
C.
railwayStationFeature
chosen
Indicates that a railway station possesses or is characterized by a particular feature, facility, or attribute.
-
D.
isRailwayStation
Indicates that the subject is a railway station, i.e., a facility where trains regularly stop to pick up or drop off passengers and/or freight.
-
E.
hasRailwayStationRole
Indicates that an entity holds or is assigned a specific functional role or capacity within the operation or management of a railway station.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 21, 2026, 8:47 p.m.