Triple
T13295461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travelcard Zones 1–5 |
E316668
|
entity |
| Predicate | hasZone |
P6793
|
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: [Travelcard Zones 1–5, hasZone, Zone 1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zone 1 Context triple: [Travelcard Zones 1–5, hasZone, 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 2
Zone 2 is a fare zone within a public transit system used to determine ticket prices and travel boundaries.
-
D.
Zone 3
Zone 3 is a mid-distance public transport fare zone in London covering various suburban residential and commercial areas outside the city center.
-
E.
Zone 3
Zone 3 is one of the MBTA Commuter Rail’s outer fare zones used to set ticket prices for trips between Boston and its surrounding suburbs.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99079c8508190b6208db9affcbc0e |
completed | April 11, 2026, 12:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f716dad3648190bf360955fbdfb2f0 |
completed | May 3, 2026, 9:35 a.m. |
Created at: April 9, 2026, 9:28 p.m.