Triple
T34759583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tooting Bec tube station |
E1002026
|
entity |
| Predicate | fareZoneStartDate |
P129036
|
FINISHED |
| Object | 1983 |
—
|
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: 1983 | Statement: [Tooting Bec tube station, fareZoneStartDate, 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareZoneStartDate Context triple: [Tooting Bec tube station, fareZoneStartDate, 1983]
-
A.
fareZoneStart
Indicates the fare zone in which a journey, ticket, or pricing calculation begins.
-
B.
fareZoneSince
chosen
Indicates the date or time from which a particular fare zone assignment has been in effect for an entity.
-
C.
fareZoneEnd
Indicates the ending boundary or final zone in a defined fare zone range for a trip or ticket.
-
D.
fareZoneUsage
Indicates how a fare zone is applied or utilized within a transportation or pricing context.
-
E.
fareZoneChangeBoundary
Indicates a boundary where the applicable fare zone changes from one zone to another.
- 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_69f76db0fb30819096709d43f9a1f45f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.