Triple

T13412640
Position Surface form Disambiguated ID Type / Status
Subject McCook County, South Dakota E320127 entity
Predicate hasCity P316 FINISHED
Object Salem, South Dakota E1128685 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: Salem, South Dakota | Statement: [McCook County, South Dakota, hasCity, Salem, South Dakota]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Salem, South Dakota
Context triple: [McCook County, South Dakota, hasCity, Salem, South Dakota]
  • A. Salem, South Dakota chosen
    Salem, South Dakota is a small city in eastern South Dakota that serves as the administrative and commercial hub of McCook County.
  • B. Madison, South Dakota
    Madison, South Dakota is a small city in eastern South Dakota known as a regional hub for education, technology, and agriculture.
  • C. Hartford, South Dakota
    Hartford, South Dakota is a small city in eastern South Dakota that serves as a growing residential community near Sioux Falls.
  • D. Frankfort, South Dakota
    Frankfort, South Dakota is a small rural town located in eastern South Dakota within the agricultural region of the state.
  • E. Columbia, South Dakota
    Columbia, South Dakota is a small rural town located in northeastern South Dakota within Brown 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_69d806b943cc8190b6af624d385d7e12 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaeb556948190af008c88e5bbf051 completed April 12, 2026, 2:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe967a96708190b8688e84fdb270b0 completed May 9, 2026, 2:05 a.m.
Created at: April 9, 2026, 9:35 p.m.