Triple
T26001388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoreditch High Street station |
E646635
|
entity |
| Predicate | inTravelcardZoneBoundary |
P108976
|
FINISHED |
| Object | Zone 1/2 boundary |
—
|
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: Zone 1/2 boundary | Statement: [Shoreditch High Street station, inTravelcardZoneBoundary, Zone 1/2 boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inTravelcardZoneBoundary Context triple: [Shoreditch High Street station, inTravelcardZoneBoundary, Zone 1/2 boundary]
-
A.
locatedInTravelcardZoneBoundary
chosen
Indicates that something lies on or within the defined boundary of a specific travelcard fare zone.
-
B.
fareZoneChangeBoundary
Indicates a boundary where the applicable fare zone changes from one zone to another.
-
C.
travelcardZoneCombination
Indicates the specific combination of fare zones in which a travelcard is valid or applicable.
-
D.
hasFareBoundary
Indicates that there is a defined limit or border beyond which a particular fare, ticket, or pricing rule no longer applies.
-
E.
fareZoneOfStationIdentified
Indicates that the specific fare zone associated with a given station has been identified.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605755bd48190a760f5301eafb3ae |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 9 a.m.