Triple

T17810090
Position Surface form Disambiguated ID Type / Status
Subject Richmond E444674 entity
Predicate writtenForm P2203 FINISHED
Object Richmond NE NERFINISHED

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: [Richmond, writtenForm, Richmond]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Richmond
Context triple: [Richmond, writtenForm, 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 historic market town in North Yorkshire, England, known for its Norman castle, cobbled marketplace, and scenic location on the River Swale.
  • 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
    Richmond is a common English surname of Norman origin, historically associated with various noble families and place names in England.
  • E. Richmond
    Richmond is a city in central Kentucky that serves as the home of Eastern Kentucky University and the seat of Madison County.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide. chosen

Provenance (2 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_69d8b9f0de78819099395b14db75a8a6 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4887a50488190b9c148146ec607e6 completed April 19, 2026, 7:47 a.m.
Created at: April 10, 2026, 10:14 a.m.