Triple
T26454492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chesham station |
E665443
|
entity |
| Predicate | servedByBusConnections |
P39381
|
FINISHED |
| Object | local bus routes in Chesham |
—
|
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: local bus routes in Chesham | Statement: [Chesham station, servedByBusConnections, local bus routes in Chesham]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByBusConnections Context triple: [Chesham station, servedByBusConnections, local bus routes in Chesham]
-
A.
accessByBusFrom
Indicates that one location can be reached from another location using a bus as the mode of transportation.
-
B.
hasBusServices
chosen
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
C.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
D.
connectsToBusAt
Indicates that one entity has an access or transfer point where it links to a bus service at a specific location or stop.
-
E.
servedByTransportation
Indicates that a location or entity is provided access or connection by a particular mode or service of transportation.
- 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 27, 2026, 12:08 a.m.