Triple
T6629910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holborn station |
E149895
|
entity |
| Predicate | fareZone |
P844
|
FINISHED |
| Object | Zone 1 |
E212175
|
NE 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: [Holborn station, fareZone, Zone 1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zone 1 Context triple: [Holborn station, fareZone, Zone 1]
-
A.
Zone 1
chosen
Zone 1 is the central London public transport fare zone that covers the city’s main commercial, tourist, and historic areas.
-
B.
Zone 1A
Zone 1A is a central MBTA subway fare zone in Boston that includes Park Street station and other core downtown stops.
-
C.
Zone 5
Zone 5 is an outer fare zone in the London public transport system used for calculating ticket and Travelcard prices.
-
D.
Zone 12
Zone 12 is an outer Long Island Rail Road fare zone used for setting ticket prices to and from stations such as Mastic–Shirley.
-
E.
Zone G
Zone G is a designated fare zone within the Glasgow Subway ticketing system that includes Kelvinbridge subway station.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c687ee50048190aa151765bef16193 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6afa5c9b48190b645be96d446d0ca |
completed | March 27, 2026, 4:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6cbeb04348190957b8e5f098b72bf |
completed | March 27, 2026, 6:26 p.m. |
Created at: March 27, 2026, 1:59 p.m.