Triple

T14326083
Position Surface form Disambiguated ID Type / Status
Subject RIC E355218 entity
Predicate servesCity P82 FINISHED
Object Richmond E69443 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: [RIC, servesCity, Richmond]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Richmond
Context triple: [RIC, servesCity, Richmond]
  • A. Richmond chosen
    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.

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_69d8278fa2108190bc0d0e7939c1eb03 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de883e6a288190b6c22f630a1eef3c completed April 14, 2026, 6:32 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd5bb5a64c81908cb8c50bbfa239a4 completed May 8, 2026, 3:42 a.m.
Created at: April 10, 2026, 1:13 a.m.