Triple
T17401803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finchley Road |
E423107
|
entity |
| Predicate | travelcardZoneBoundary |
P44473
|
FINISHED |
| Object | between Zone 2 and 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: between Zone 2 and Zone 3 | Statement: [Finchley Road, travelcardZoneBoundary, between Zone 2 and Zone 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelcardZoneBoundary Context triple: [Finchley Road, travelcardZoneBoundary, between Zone 2 and Zone 3]
-
A.
locatedInTravelcardZoneBoundary
Indicates that something lies on or within the defined boundary of a specific travelcard fare zone.
-
B.
travelcardZoneCombination
Indicates the specific combination of fare zones in which a travelcard is valid or applicable.
-
C.
hasBoundaryStations
Indicates that an entity is associated with specific stations that mark its boundary or endpoints.
-
D.
hasFareBoundary
Indicates that there is a defined limit or border beyond which a particular fare, ticket, or pricing rule no longer applies.
-
E.
fareBoundaryBetween
chosen
Indicates that there is a dividing line or zone where one fare region, zone, or pricing scheme ends and another begins.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43b046ad88190a95bbeda4e602514 |
completed | April 19, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.