Triple

T15396629
Position Surface form Disambiguated ID Type / Status
Subject Theodore of Tarsus E368193 entity
Predicate deathPlace P21 FINISHED
Object Canterbury E72201 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: Canterbury | Statement: [Theodore of Tarsus, deathPlace, Canterbury]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Canterbury
Context triple: [Theodore of Tarsus, deathPlace, Canterbury]
  • A. Canterbury
    Canterbury is a large region on New Zealand’s South Island, centered on the city of Christchurch and known for its expansive plains, alpine scenery, and diverse communities.
  • B. Canterbury chosen
    Canterbury is a historic cathedral city in Kent, England, renowned for its medieval architecture and status as a major center of Christian pilgrimage.
  • C. Canterbury
    Canterbury is a renowned New Zealand-founded sportswear brand best known for producing high-performance rugby apparel and kits for top international teams.
  • D. Bristol
    Bristol is a small town located in Dane County in the U.S. state of Wisconsin.
  • E. Bristol
    Bristol is a small community within the town of East Gwillimbury in Ontario, Canada.
  • 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_69d85a16c68c819099c1b547fbc87b32 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03e8c5d40819086622b70edcb6294 completed April 16, 2026, 1:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff13542c908190abf765b0530c76ce completed May 9, 2026, 10:58 a.m.
Created at: April 10, 2026, 3:19 a.m.