Triple

T21256964
Position Surface form Disambiguated ID Type / Status
Subject Battle of Sharpsburg E523893 entity
Predicate tookPlaceNear P350 FINISHED
Object Antietam Creek 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: Antietam Creek | Statement: [Battle of Sharpsburg, tookPlaceNear, Antietam Creek]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Antietam Creek
Context triple: [Battle of Sharpsburg, tookPlaceNear, Antietam Creek]
  • A. Antietam Creek chosen
    Antietam Creek is a tributary of the Potomac River in Pennsylvania and Maryland, historically notable for its proximity to the American Civil War Battle of Antietam.
  • B. Paynes Creek
    Paynes Creek is a small unincorporated rural community located in Tehama County in northern California.
  • C. Falling Creek
    Falling Creek is a smaller stream in Virginia that feeds into the Appomattox River as one of its tributaries.
  • D. Starrucca Creek
    Starrucca Creek is a stream in northeastern Pennsylvania known for being spanned by the historic stone-arch Starrucca Viaduct.
  • E. Monocacy Creek
    Monocacy Creek is a small stream in Berks County, Pennsylvania, that serves as a local waterway flowing through rural townships such as Amity Township.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69e0b5146c108190adc9adb73e90abff completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e735e2f1d48190b566ab4d736fdbc4 completed April 21, 2026, 8:31 a.m.
Created at: April 16, 2026, 3:58 p.m.