Triple

T6123160
Position Surface form Disambiguated ID Type / Status
Subject Southern Indiana E136530 entity
Predicate contains P35 FINISHED
Object Jasper, Indiana E67338 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: Jasper, Indiana | Statement: [Southern Indiana, contains, Jasper, Indiana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jasper, Indiana
Context triple: [Southern Indiana, contains, Jasper, Indiana]
  • A. Jasper, Indiana, United States chosen
    Jasper, Indiana, United States, is a small city in Dubois County known for its strong German heritage, manufacturing base, and vibrant high school athletics culture.
  • B. Jacksonburg, Indiana
    Jacksonburg, Indiana is a small unincorporated rural community located in Wayne County in the eastern part of the state.
  • C. La Paz, Indiana
    La Paz, Indiana is a small Midwestern town located in northern Indiana within Marshall County.
  • D. Rochester, Indiana
    Rochester, Indiana is a small city in Fulton County that serves as the county seat and a local hub for the surrounding rural region in northern Indiana.
  • E. Winfield, Indiana
    Winfield, Indiana is a small suburban town in northwest Indiana known for its residential communities and proximity to the Chicago metropolitan area.
  • 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_69c0089f851c81909e5e189a617dcff6 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c05c247b7081909972b40afb165e6f completed March 22, 2026, 9:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69c135abcef08190a899d7ba261ebb04 completed March 23, 2026, 12:44 p.m.
Created at: March 22, 2026, 4:14 p.m.