Triple

T14022972
Position Surface form Disambiguated ID Type / Status
Subject Lakeside E337381 entity
Predicate locatedNear P294 FINISHED
Object Richmond, Virginia E8109 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, Virginia | Statement: [Lakeside, locatedNear, Richmond, Virginia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Richmond, Virginia
Context triple: [Lakeside, locatedNear, Richmond, Virginia]
  • A. Richmond, Virginia chosen
    Richmond, Virginia is the capital city of the U.S. state of Virginia, known for its pivotal role in American history, particularly as the capital of the Confederacy during the Civil War.
  • 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 a historic outer suburb of Sydney, New South Wales, known for its semi-rural character and proximity to the Hawkesbury River.
  • 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_69d81c6543a48190bd5ba93d7419e797 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2f3d87b88190b038d334f4965369 completed April 14, 2026, 12:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd192ee1ac81908663ebd2e06784f1 completed May 7, 2026, 10:58 p.m.
Created at: April 9, 2026, 10:19 p.m.