Triple

T6253229
Position Surface form Disambiguated ID Type / Status
Subject TW postcode area E140097 entity
Predicate coversTown P847 FINISHED
Object Richmond E333581 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: Richmond | Statement: [TW postcode area, coversTown, Richmond]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Richmond
Context triple: [TW postcode area, coversTown, Richmond]
  • A. Richmond
    Richmond is an industrial and residential city in California’s East Bay region, known for its waterfront along San Francisco Bay and its diverse, working-class communities.
  • B. Richmond
    Richmond is a masculine given name of English origin that has been borne by various notable figures, including military leaders and public officials.
  • C. Richmond chosen
    Richmond is a historic market town in North Yorkshire, England, known for its Norman castle, cobbled marketplace, and scenic location on the River Swale.
  • D. Richmond
    Richmond is an Australian federal electoral division in northern New South Wales that includes coastal communities such as Tweed Heads and Byron Bay.
  • E. Richmond
    Richmond is a common English surname of Norman origin, historically associated with various noble families and place names in England.
  • 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_69c008b4858c819095b0199114a9a87b completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c063417c8c8190945049881819d307 completed March 22, 2026, 9:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69c62cf2edd48190b3d5f6bf27075fed completed March 27, 2026, 7:08 a.m.
Created at: March 22, 2026, 4:24 p.m.