Triple

T15632660
Position Surface form Disambiguated ID Type / Status
Subject Lonesome Jim E375854 entity
Predicate filmingLocation P40 FINISHED
Object Goshen, Indiana E683963 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: Goshen, Indiana | Statement: [Lonesome Jim, filmingLocation, Goshen, Indiana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Goshen, Indiana
Context triple: [Lonesome Jim, filmingLocation, Goshen, Indiana]
  • A. Goshen, Indiana, United States
    Goshen, Indiana, United States is a small Midwestern city known as the county seat of Elkhart County and for its manufacturing and agricultural industries.
  • B. Greensburg, Indiana
    Greensburg, Indiana is a small Midwestern city known for its historic courthouse square and the famous tree growing from the Decatur County Courthouse tower.
  • C. Goshen
    Goshen is a small town in Utah County, Utah, situated in the southern part of Utah Valley.
  • D. Goshen
    Goshen is the fertile region in ancient Egypt where the Israelites settled during the time of Joseph, as recounted in the Book of Genesis.
  • E. Goshen chosen
    Goshen is a small city in northern Indiana known for its manufacturing base, Mennonite and Amish heritage, and historic downtown.
  • 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_69d85cd035a48190b73d5579ab73969a completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04eb7338881909f3c430bb73f91d1 completed April 16, 2026, 2:51 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff5f472b648190b7cd532a1b16373e completed May 9, 2026, 4:22 p.m.
Created at: April 10, 2026, 4:14 a.m.