Triple
T27855719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haddenham and Thame Parkway |
E704077
|
entity |
| Predicate | hasParkAndRideRoleFor |
P24860
|
FINISHED |
| Object | Thame |
—
|
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: Thame | Statement: [Haddenham and Thame Parkway, hasParkAndRideRoleFor, Thame]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParkAndRideRoleFor Context triple: [Haddenham and Thame Parkway, hasParkAndRideRoleFor, Thame]
-
A.
hasParkAndRideFunction
chosen
Indicates that a location or facility serves as a park-and-ride, where people can park vehicles and transfer to another mode of transport for the rest of their journey.
-
B.
hasParkAndRideGarage
Indicates that a location includes a parking facility where people can park their vehicles and transfer to public transit services.
-
C.
hasPublicTransitRole
Indicates that an entity holds a specific functional role or responsibility within a public transit system.
-
D.
hasParkAccess
Indicates that an entity is permitted to enter, use, or otherwise access a specified park or park area.
-
E.
hasParkingFor
Indicates that a place or facility provides designated parking spaces suitable for a specified type of vehicle or user.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 27, 2026, 6:14 p.m.