Triple

T995192
Position Surface form Disambiguated ID Type / Status
Subject Manchester–Chester line E21479 entity
Predicate via P5680 FINISHED
Object Sale E67553 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: Sale | Statement: [Manchester–Chester line, via, Sale]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sale
Context triple: [Manchester–Chester line, via, Sale]
  • A. Sale chosen
    Sale is a town in Greater Manchester, England, known as a residential suburb within the Metropolitan Borough of Trafford.
  • B. Venta
    Venta is a major river in the Baltic region that flows through western Latvia and Lithuania before emptying into the Baltic Sea.
  • C. Deal
    Deal is a historic coastal town and former fishing and mining port in the county of Kent in southeast England, known for its pier, maritime heritage, and role in coastal defense.
  • D. Venda
    Venda is a Bantu language of the Venda people of South Africa and Zimbabwe, recognized as one of South Africa’s official languages.
  • E. Marketplace
    Marketplace is a long-running public radio program and podcast focused on in-depth coverage and analysis of business, economic, and financial news.
  • 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_69a493c476b48190b41fc5e793171cc6 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b4c75de88190bf7fec7a053f7a90 completed March 1, 2026, 9:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac25919bcc8190886f19405536681b completed March 7, 2026, 1:18 p.m.
Created at: March 1, 2026, 7:41 p.m.