Triple

T5400237
Position Surface form Disambiguated ID Type / Status
Subject Exeter Cathedral Library E120755 entity
Predicate locatedIn P40 FINISHED
Object Exeter E122858 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: Exeter | Statement: [Exeter Cathedral Library, locatedIn, Exeter]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Exeter
Context triple: [Exeter Cathedral Library, locatedIn, Exeter]
  • A. Exeter chosen
    Exeter is a historic cathedral city in Devon, England, known for its medieval architecture and role as a regional administrative and cultural center.
  • B. Exeter
    Exeter is a historic town in Rockingham County, New Hampshire, known for its colonial heritage and as the home of the prestigious Phillips Exeter Academy.
  • C. Bristol
    Bristol is a city in central Connecticut known for being the home of ESPN and for its historic clock-making industry.
  • D. Bristol
    Bristol is a city in central Connecticut known historically for its clock-making industry and as the longtime home of ESPN’s headquarters.
  • E. Bristol
    Bristol is a small town located in Dane County in the U.S. state of Wisconsin.
  • 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_69bd4637b92c8190b815b6443ae4b323 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd8770809c8190bb387ef04ffa794c completed March 20, 2026, 5:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf3a9e104881908d6012c87f30061b completed March 22, 2026, 12:41 a.m.
Created at: March 20, 2026, 2:04 p.m.