Triple

T6460744
Position Surface form Disambiguated ID Type / Status
Subject Chapter of Hereford Cathedral E142113 entity
Predicate locatedIn P40 FINISHED
Object Hereford E65056 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: Hereford | Statement: [Chapter of Hereford Cathedral, locatedIn, Hereford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hereford
Context triple: [Chapter of Hereford Cathedral, locatedIn, Hereford]
  • A. Hereford chosen
    Hereford is a cathedral city in Herefordshire, England, known for its historic architecture and role as a military and agricultural center.
  • B. Hereford
    Hereford is a small city in the Texas Panhandle known for its strong agricultural and cattle industry.
  • C. Wellington, Shropshire
    Wellington, Shropshire is a historic market town in Shropshire, England, now part of the new town of Telford.
  • D. Swindon
    Swindon is a large town in Wiltshire, England, known as a major commercial and commuter hub in the southwest with strong railway and industrial heritage.
  • E. Yate
    Yate is a town in South Gloucestershire, England, known as a residential and commercial centre north of Bristol.
  • 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_69c008d2f91c8190a8178767a35e08fc completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c069f50ea88190af29c8c249ff2b69 completed March 22, 2026, 10:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69c653971f988190847187ae60b6eeb5 completed March 27, 2026, 9:53 a.m.
Created at: March 22, 2026, 4:48 p.m.