Triple
T23854909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monks Risborough |
E592276
|
entity |
| Predicate | hasRailServiceAt |
P154206
|
FINISHED |
| Object | Princes Risborough railway station |
—
|
NE NERFINISHED |
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: Princes Risborough railway station | Statement: [Monks Risborough, hasRailServiceAt, Princes Risborough railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailServiceAt Context triple: [Monks Risborough, hasRailServiceAt, Princes Risborough railway station]
-
A.
isRailServiceOf
Indicates that a particular rail service operates for, belongs to, or is provided by a specified entity (such as a route, operator, or network).
-
B.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
-
C.
hasRegionalTrainService
Indicates that a location or route is served by regional train services connecting it to nearby areas.
-
D.
hasNightTrainService
Indicates that a transportation route or station is served by trains that operate during nighttime hours.
-
E.
hasAdjacentRailService
Indicates that one location has rail service situated directly next to or immediately bordering it.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c98a60b081908dbdc359f51e67fa |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:11 p.m.