Triple

T10691900
Position Surface form Disambiguated ID Type / Status
Subject Petersham E252030 entity
Predicate locatedSouthOf P9676 FINISHED
Object Richmond E430166 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: [Petersham, locatedSouthOf, Richmond]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Richmond
Context triple: [Petersham, locatedSouthOf, 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
    Richmond is an Australian federal electoral division in northern New South Wales that includes coastal communities such as Tweed Heads and Byron Bay.
  • D. Richmond chosen
    Richmond is a historic outer suburb of Sydney, New South Wales, known for its semi-rural character and proximity to the Hawkesbury River.
  • E. Richmond
    Richmond is a small settlement located in St. Mary Parish on the northern coast of Jamaica.
  • 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_69d6aa5bd7c08190a816e733b4045c23 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6fd37cf408190a1912b3e0aa096a5 completed April 9, 2026, 1:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69deb07626988190a46d8a54eda156f5 completed April 14, 2026, 9:24 p.m.
Created at: April 8, 2026, 9:11 p.m.