Triple
T1902145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Cannon Street |
E37712
|
entity |
| Predicate | travelcardZone |
P17300
|
FINISHED |
| Object | Zone 1 |
—
|
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: Zone 1 | Statement: [London Cannon Street, travelcardZone, Zone 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelcardZone Context triple: [London Cannon Street, travelcardZone, Zone 1]
-
A.
travelsOn
Indicates that an entity moves or journeys using a particular route, path, or mode of transportation.
-
B.
railwayRegion
Indicates a relationship where a railway or rail network is associated with, located in, or administered within a particular geographic region.
-
C.
publicTransportZone
chosen
Indicates that an entity is located within, associated with, or valid for a specific public transportation fare or service zone.
-
D.
touringArea
Indicates that an entity is designated as an area or region where touring or guided visits take place.
-
E.
tourismRegion
Indicates that a place or area is designated or recognized as a tourism region associated with another geographic or administrative entity.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafe9f8b0819086d8f6288511c66d |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.