Triple
T9629529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boylston |
E232560
|
entity |
| Predicate | fareZone |
P844
|
FINISHED |
| Object | Zone 1A |
E127549
|
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 1A | Statement: [Boylston, fareZone, Zone 1A]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zone 1A Context triple: [Boylston, fareZone, Zone 1A]
-
A.
Zone 1A
chosen
Zone 1A is a central MBTA subway fare zone in Boston that includes Park Street station and other core downtown stops.
-
B.
Zone 1
Zone 1 is the central London public transport fare zone that covers the city’s main commercial, tourist, and historic areas.
-
C.
Zona A
Zona A was the Allied-administered western sector of the Free Territory of Trieste, encompassing the city of Trieste and surrounding areas after World War II.
-
D.
Zone L (Guthrie classification)
Zone L in the Guthrie classification is a group of closely related Bantu languages centered around Tshiluba and its dialects in south-central Africa.
-
E.
Zone 5
Zone 5 is an outer fare zone in the London public transport system used for calculating ticket and Travelcard prices.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b00162481908f396f6b6e470d6c |
completed | April 1, 2026, 10:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d17987e4008190a8d43641072a1c86 |
completed | April 4, 2026, 8:50 p.m. |
Created at: March 30, 2026, 8:10 p.m.