Triple

T4146878
Position Surface form Disambiguated ID Type / Status
Subject Hamilton Old Parish Church E89805 entity
Predicate isLandmarkOf P6629 FINISHED
Object Hamilton E92442 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: Hamilton | Statement: [Hamilton Old Parish Church, isLandmarkOf, Hamilton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hamilton
Context triple: [Hamilton Old Parish Church, isLandmarkOf, Hamilton]
  • A. Hamilton
    Hamilton is a major industrial port city in Ontario, Canada, known for its steel production and location on the western tip of Lake Ontario.
  • B. Hamilton
    Hamilton is a small city in western Georgia that serves as the administrative and cultural hub of Harris County.
  • C. Hamilton
    Hamilton is a masculine given name of English and Scottish origin, used both as a first name and a surname.
  • D. Hamilton chosen
    Hamilton is a major inland city in New Zealand’s Waikato region, known for its role as an agricultural, educational, and commercial hub on the North Island.
  • E. Hamilton
    Hamilton is a railway station in New South Wales, Australia, serving the inner western suburbs of Newcastle.
  • 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_69aed95a59a881909b26e70b42c6811a completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af026130bc8190ae3b0e9bec5ccad6 completed March 9, 2026, 5:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69b57f256abc819086cd464be1a9efbf completed March 14, 2026, 3:30 p.m.
Created at: March 9, 2026, 3:43 p.m.