Triple
T12724981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnos Grove |
E304080
|
entity |
| Predicate | hasStepFreeAccessToTicketHall |
P3790
|
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: [Arnos Grove, hasStepFreeAccessToTicketHall, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStepFreeAccessToTicketHall Context triple: [Arnos Grove, hasStepFreeAccessToTicketHall, yes]
-
A.
hasStepFreeAccess
chosen
Indicates that a location, facility, or route can be accessed without using stairs, typically via ramps, lifts, or level entrances.
-
B.
hasTicketHall
Indicates that a place or facility includes or is equipped with a designated ticket hall area for purchasing or validating tickets.
-
C.
accessibleWithoutParkTicket
Indicates that a location, attraction, or service can be reached or used without requiring a park admission ticket.
-
D.
hasRampSpace
Indicates that a location or structure includes designated space for a ramp, allowing sloped access between different levels.
-
E.
hasWheelchairSpace
Indicates that an object, location, or vehicle includes designated space that can accommodate a wheelchair 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:25 p.m.