Triple

T13192736
Position Surface form Disambiguated ID Type / Status
Subject Earl's Court E314032 entity
Predicate locatedInTravelcardZoneBoundary P108976 FINISHED
Object boundary between Zone 1 and Zone 2 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: boundary between Zone 1 and Zone 2 | Statement: [Earl's Court, locatedInTravelcardZoneBoundary, boundary between Zone 1 and Zone 2]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInTravelcardZoneBoundary
Context triple: [Earl's Court, locatedInTravelcardZoneBoundary, boundary between Zone 1 and Zone 2]
  • A. fareZoneIncludes
    Indicates that a specified fare zone geographically or logically contains a given location, stop, or segment for fare calculation purposes.
  • B. isWithinLondonFareSystem
    Indicates that an entity (such as a station, stop, or route) is located inside the area covered by the London public transport fare system.
  • C. fareZoneFromCentralLondon
    Indicates the public transport fare zone in which a location lies, measured relative to central London.
  • D. hasFareBoundary
    Indicates that there is a defined limit or border beyond which a particular fare, ticket, or pricing rule no longer applies.
  • E. hasFareZone
    Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
  • 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_69d806ae1e08819090d95bfe1538cc17 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98cf054f88190b05ced98d5a22a62 completed April 10, 2026, 11:51 p.m.
PD Predicate disambiguation batch_69d98bc6bc108190b5a6a265bf6e9fd4 completed April 10, 2026, 11:46 p.m.
PDg Predicate description generation batch_69d98ceeb22c8190a6be666031d9e5a4 completed April 10, 2026, 11:51 p.m.
Created at: April 9, 2026, 9:16 p.m.