Triple

T8746579
Position Surface form Disambiguated ID Type / Status
Subject Hendricks County, Indiana E207842 entity
Predicate hasTown P847 FINISHED
Object Pittsboro, Indiana E729309 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: Pittsboro, Indiana | Statement: [Hendricks County, Indiana, hasTown, Pittsboro, Indiana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pittsboro, Indiana
Context triple: [Hendricks County, Indiana, hasTown, Pittsboro, Indiana]
  • A. Pittsboro, Indiana chosen
    Pittsboro, Indiana is a small town in central Indiana that forms part of the Indianapolis metropolitan area.
  • B. Woodburn, Indiana
    Woodburn, Indiana is a small city in northeastern Indiana known as one of the easternmost communities in Allen County near the Ohio border.
  • C. Walkerton, Indiana
    Walkerton, Indiana is a small town in northern Indiana known for its rural character and proximity to the South Bend metropolitan area.
  • D. Pawnee, Indiana
    Pawnee, Indiana is the fictional Midwestern town that serves as the primary setting for the television comedy series "Parks and Recreation."
  • E. Lizton, Indiana
    Lizton, Indiana is a small rural town in central Indiana known for its close-knit community and location within the Indianapolis 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_69ca835bb2bc819084bb5906cb6ef7f8 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5d75e7c88190a9e78fadb979e1b6 completed March 31, 2026, 11:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69cfeafd26f4819092f5adc1ac70148f completed April 3, 2026, 4:29 p.m.
Created at: March 30, 2026, 6:39 p.m.