Triple
T34848486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tooting Broadway tube station |
E1004535
|
entity |
| Predicate | fareZoneClassification |
P155236
|
FINISHED |
| Object | Travelcard Zone 3 |
—
|
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 3 | Statement: [Tooting Broadway tube station, fareZoneClassification, Travelcard Zone 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareZoneClassification Context triple: [Tooting Broadway tube station, fareZoneClassification, Travelcard Zone 3]
-
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.
fareZoneAuthority
Indicates that an authority or organization is responsible for defining, managing, or overseeing a specific fare zone.
-
D.
fareZoneOfStationIdentified
chosen
Indicates that the specific fare zone associated with a given station has been identified.
-
E.
fareZoneRange
Indicates the range of fare zones within which a ticket, pass, or fare rule is valid or applicable.
- 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.