Triple

T4301669
Position Surface form Disambiguated ID Type / Status
Subject Duke of Abercorn E99850 entity
Predicate familyName P18 FINISHED
Object Hamilton E17790 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: [Duke of Abercorn, familyName, Hamilton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hamilton
Context triple: [Duke of Abercorn, familyName, Hamilton]
  • A. Hamilton chosen
    Hamilton is a masculine given name of English and Scottish origin, used both as a first name and a surname.
  • B. 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.
  • C. Hamilton
    Hamilton is a small city in western Georgia that serves as the administrative and cultural hub of Harris County.
  • D. Hamilton
    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_69b345528ebc8190b5abc7e95094792d completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b3509fb2b88190a13ab88a5b924052 completed March 12, 2026, 11:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5c739df2c8190af6f8d9bf36afca8 completed March 14, 2026, 8:38 p.m.
Created at: March 12, 2026, 11:08 p.m.