Triple
T11943298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walthamstow Central |
E284230
|
entity |
| Predicate | fareZone |
P844
|
FINISHED |
| Object | Zone 3 |
E733980
|
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 3 | Statement: [Walthamstow Central, fareZone, Zone 3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zone 3 Context triple: [Walthamstow Central, fareZone, Zone 3]
-
A.
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.
-
B.
Zone 3
chosen
Zone 3 is one of the concentric public transport fare zones in the Île-de-France region surrounding central Paris.
-
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 1
Zone 1 is the central London public transport fare zone that covers the city’s main commercial, tourist, and historic areas.
-
E.
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.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9034444488190925a6fa6c856ed08 |
completed | April 10, 2026, 2:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f440a5a9c8819086a94ad60c6881b8 |
completed | May 1, 2026, 5:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.