Triple

T5858974
Position Surface form Disambiguated ID Type / Status
Subject Medway E130226 entity
Predicate containsHistoricCity P3786 FINISHED
Object Rochester E116344 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: Rochester | Statement: [Medway, containsHistoricCity, Rochester]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rochester
Context triple: [Medway, containsHistoricCity, Rochester]
  • A. Rochester
    Rochester is a major city in western New York State known historically for its role in industry, photography, and social reform movements.
  • B. Rochester chosen
    Rochester is a historic cathedral city and former market town in Kent, England, known for its Norman castle, Romanesque cathedral, and strong associations with the novelist Charles Dickens.
  • C. Rochester
    Rochester is a small borough in western Pennsylvania situated along the Ohio River in Beaver County.
  • D. Rochester
    Rochester is a small historic town in southeastern Massachusetts known for its rural character and New England charm.
  • E. Rochester
    Rochester is a major city in southeastern Minnesota known for being the home of the world-renowned Mayo Clinic.
  • 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_69c0084f3bb08190a7720f55f7aa4252 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0358654e48190908e7390a0164726 completed March 22, 2026, 6:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69c65373f5388190bb2da987d6d24d23 completed March 27, 2026, 9:52 a.m.
Created at: March 22, 2026, 3:56 p.m.