Triple

T14029124
Position Surface form Disambiguated ID Type / Status
Subject Jasper Parklands E337539 entity
Predicate locatedIn P40 FINISHED
Object Jasper, Indiana E1074865 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: [Jasper Parklands, locatedIn, Jasper, Indiana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jasper, Indiana
Context triple: [Jasper Parklands, locatedIn, Jasper, Indiana]
  • A. Jasper, Indiana chosen
    Jasper, Indiana is a small city in southwestern Indiana known for its strong German heritage, manufacturing base, and historic attractions along the Patoka River.
  • B. Jacksonburg, Indiana
    Jacksonburg, Indiana is a small unincorporated rural community located in Wayne County in the eastern part of the state.
  • C. St. John, Indiana
    St. John, Indiana is a suburban town in Lake County known for its residential communities, good schools, and proximity to the Chicago metropolitan area.
  • D. Jamestown, Indiana
    Jamestown, Indiana is a small town in central Indiana known for its rural character and tight-knit community.
  • E. Jasonville, Indiana
    Jasonville, Indiana is a small city in southwestern Indiana known historically for its coal mining roots and close-knit rural community.
  • 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_69de2fa9f8248190930954d609dee5f1 completed April 14, 2026, 12:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcb657ab348190ab51ec0e8caa2c4f completed May 7, 2026, 3:57 p.m.
Created at: April 9, 2026, 10:20 p.m.