Triple
T11396006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queenstown Road area |
E269973
|
entity |
| Predicate | withinTravelZone |
P69645
|
FINISHED |
| Object | London 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: London Travelcard Zone 2 | Statement: [Queenstown Road area, withinTravelZone, London Travelcard Zone 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withinTravelZone Context triple: [Queenstown Road area, withinTravelZone, London Travelcard Zone 2]
-
A.
fareZoneIncludes
chosen
Indicates that a specified fare zone geographically or logically contains a given location, stop, or segment for fare calculation purposes.
-
B.
containsTouristArea
Indicates that a place or region includes within its boundaries an area primarily designated or recognized for tourism activities.
-
C.
travelsThrough
Indicates that something moves along, passes across, or is routed via a particular path, medium, or location.
-
D.
isWithinResort
Indicates that one place, object, or activity is located inside the boundaries of a specific resort.
-
E.
placesWithin
Indicates that one place or area is located entirely inside the boundaries of another place or area.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80018a58c81908b80dc9abd18d650 |
completed | April 9, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.