Triple

T20943886
Position Surface form Disambiguated ID Type / Status
Subject Winchcombe railway station E515792 entity
Predicate hasLevelAccessFromCarPark P141790 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: [Winchcombe railway station, hasLevelAccessFromCarPark, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLevelAccessFromCarPark
Context triple: [Winchcombe railway station, hasLevelAccessFromCarPark, yes]
  • A. hasParkAccess
    Indicates that an entity is permitted to enter, use, or otherwise access a specified park or park area.
  • B. hasVehicleAccess
    Indicates that an entity is permitted to use or enter a particular vehicle.
  • C. hasParkingFor
    Indicates that a place or facility provides designated parking spaces suitable for a specified type of vehicle or user.
  • D. hasParkStatus
    Indicates that an entity holds a particular designation or status related to being a park (e.g., national park, city park, protected parkland).
  • E. hasPrimaryVehicularAccessTo
    Indicates that one location or entity serves as the main route or means by which vehicles can reach or enter another location or entity.
  • 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_69e0b4fc13408190b06868df03c5c29b completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6f95838708190978dfa8bc786fb22 completed April 21, 2026, 4:13 a.m.
PD Predicate disambiguation batch_69e5c9b1bae48190a845165fed1b005e completed April 20, 2026, 6:37 a.m.
PDg Predicate description generation batch_69e5d53d22d08190bc17ed4bed53804a completed April 20, 2026, 7:26 a.m.
Created at: April 16, 2026, 12:52 p.m.