Triple

T11414516
Position Surface form Disambiguated ID Type / Status
Subject Mornington Crescent E270455 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: [Mornington Crescent, fareZone, Zone 1]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zone 1
Context triple: [Mornington Crescent, 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 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.
  • D. Zone 3
    Zone 3 is one of the concentric public transport fare zones in the Île-de-France region surrounding central Paris.
  • E. 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.
  • 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_69d6aaddeaa8819088b30ef7b50598c9 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d801ae47d0819098123505309c4a68 completed April 9, 2026, 7:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69e5b86936348190b8fa4125995c2a85 completed April 20, 2026, 5:23 a.m.
Created at: April 8, 2026, 9:34 p.m.