Triple

T21158002
Position Surface form Disambiguated ID Type / Status
Subject IN-2 E521361 entity
Predicate contains P35 FINISHED
Object Mishawaka, Indiana NE NERFINISHED

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: Mishawaka, Indiana | Statement: [IN-2, contains, Mishawaka, Indiana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mishawaka, Indiana
Context triple: [IN-2, contains, Mishawaka, Indiana]
  • A. Mishawaka, Indiana chosen
    Mishawaka, Indiana is a city in northern Indiana near South Bend, known for its manufacturing history and as the longtime base of vehicle maker AM General.
  • B. Pierceton, Indiana
    Pierceton, Indiana is a small town in northern Indiana known for its antique shops and rural Midwestern community character.
  • C. Madison, Indiana
    Madison, Indiana is a historic river town on the Ohio River known for its well-preserved 19th-century architecture and vibrant small-town cultural life.
  • D. Wabash, Indiana
    Wabash, Indiana is a small Midwestern city known for its historic downtown and for being one of the first electrically lighted cities in the world.
  • E. Westville, Indiana
    Westville, Indiana is a small town in northwestern Indiana known for its rural character and proximity to larger cities like Michigan City and South Bend.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b50d1ea481909c07e63c3ead9316 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7252dc3f0819094c6acf52a9f308d completed April 21, 2026, 7:20 a.m.
Created at: April 16, 2026, 2:59 p.m.