Triple
T24219782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HBY |
E601414
|
entity |
| Predicate | fareZoneOfStationIdentified |
P155236
|
FINISHED |
| Object | Travelcard 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: Travelcard Zone 2 | Statement: [HBY, fareZoneOfStationIdentified, Travelcard Zone 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareZoneOfStationIdentified Context triple: [HBY, fareZoneOfStationIdentified, Travelcard 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.
fareZoneDescription
Indicates the textual description of the fare zone associated with a service, location, or segment.
-
C.
fareZoneStart
Indicates the fare zone in which a journey, ticket, or pricing calculation begins.
-
D.
fareZoneEnd
Indicates the ending boundary or final zone in a defined fare zone range for a trip or ticket.
-
E.
fareZoneRange
Indicates the range of fare zones within which a ticket, pass, or fare rule is valid or applicable.
- 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f2820cdd3c8190998d6d901224c09f |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 17, 2026, 11:59 p.m.