Triple

T4433281
Position Surface form Disambiguated ID Type / Status
Subject Bristol City Council E95584 entity
Predicate governs P760 FINISHED
Object City of Bristol E16444 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: City of Bristol | Statement: [Bristol City Council, governs, City of Bristol]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: City of Bristol
Context triple: [Bristol City Council, governs, City of Bristol]
  • A. Bristol chosen
    Bristol is a historic port city in southwest England known for its maritime heritage, vibrant cultural scene, and distinctive Georgian and Victorian architecture.
  • B. Bristol
    Bristol is a city in central Connecticut known for being the home of ESPN and for its historic clock-making industry.
  • C. Bristol
    Bristol is a city in central Connecticut known historically for its clock-making industry and as the longtime home of ESPN’s headquarters.
  • D. Bristol
    Bristol is a small town located in Dane County in the U.S. state of Wisconsin.
  • E. Glocester
    Glocester is a rural town in northwestern Rhode Island known for its historic villages, woodlands, and small-town New England character.
  • 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_69b3453ea2b48190a26f154b3b8fece5 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b35587bc048190aee8e0ed94b6e064 completed March 13, 2026, 12:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69b6137171148190b77a6f783d5cf315 completed March 15, 2026, 2:03 a.m.
Created at: March 12, 2026, 11:31 p.m.