Triple

T8879475
Position Surface form Disambiguated ID Type / Status
Subject Chesterton, Indiana E211371 entity
Predicate adjacentTo P224 FINISHED
Object Porter, Indiana E86626 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: Porter, Indiana | Statement: [Chesterton, Indiana, adjacentTo, Porter, Indiana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Porter, Indiana
Context triple: [Chesterton, Indiana, adjacentTo, Porter, Indiana]
  • A. Porter, Indiana chosen
    Porter, Indiana is a small town in northwest Indiana near the shores of Lake Michigan, known as a gateway community to the Indiana Dunes.
  • B. La Porte, Indiana
    La Porte, Indiana is a small Midwestern city in northwestern Indiana known for its historic downtown, surrounding lakes, and role as a regional industrial and commercial center.
  • C. Southport, Indiana
    Southport, Indiana is a small incorporated city located on the south side of Indianapolis within Marion County.
  • D. Plymouth, Indiana
    Plymouth, Indiana is a small Midwestern city in northern Indiana known as a local commercial and cultural hub for the surrounding rural region.
  • E. Kouts, Indiana
    Kouts, Indiana is a small rural town located in northwestern Indiana within the Chicago metropolitan region.
  • 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_69ca838e78748190934d82db3104f855 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc614ad1908190a77808fcf7f3e531 completed April 1, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69d065b51dd881908a7cb8c02562801b completed April 4, 2026, 1:13 a.m.
Created at: March 30, 2026, 6:52 p.m.