Triple

T6818166
Position Surface form Disambiguated ID Type / Status
Subject David Richmond E156823 entity
Predicate familyName P18 FINISHED
Object Richmond E102749 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: [David Richmond, familyName, Richmond]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Richmond
Context triple: [David Richmond, familyName, Richmond]
  • A. Richmond
    Richmond is a historic outer suburb of Sydney, New South Wales, known for its semi-rural character and proximity to the Hawkesbury River.
  • B. 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.
  • C. Richmond
    Richmond is a town in southwest London, England, known for its historic riverside, expansive parkland, and affluent residential character.
  • D. Richmond chosen
    Richmond is a masculine given name of English origin that has been borne by various notable figures, including military leaders and public officials.
  • E. Richmond
    Richmond is a coastal city in Metro Vancouver, British Columbia, known for its large Asian community, busy international airport, and extensive dike-protected waterfront.
  • 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_69c688298a288190af3f285d57f76bbe completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d355b52081909f037cec76bdccf6 completed March 27, 2026, 6:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69c72f6db074819089795c29cb4f6699 completed March 28, 2026, 1:31 a.m.
Created at: March 27, 2026, 2:17 p.m.