Triple

T22745425
Position Surface form Disambiguated ID Type / Status
Subject Ulen, Indiana E562540 entity
Predicate hasOfficialName P66 FINISHED
Object Ulen, 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: Ulen, Indiana | Statement: [Ulen, Indiana, hasOfficialName, Ulen, Indiana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ulen, Indiana
Context triple: [Ulen, Indiana, hasOfficialName, Ulen, Indiana]
  • A. Ulen, Indiana chosen
    Ulen, Indiana is a small town located within Boone County that is part of the Indianapolis metropolitan area.
  • B. Loogootee, Indiana
    Loogootee, Indiana is a small city in southwestern Indiana known for its tight-knit community and strong high school basketball tradition.
  • C. Apalona, Indiana
    Apalona, Indiana is an unincorporated rural community located in Perry County in the southern part of the state.
  • D. Azalia, Indiana
    Azalia, Indiana is a small unincorporated rural community located in Bartholomew County in the U.S. state of Indiana.
  • E. Majenica, Indiana
    Majenica, Indiana is an unincorporated rural community located in Huntington County in the U.S. state of Indiana.
  • 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_69e245513a5c81908d5cb471b4fc429d completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f179b563e481908804d07fca1777b9 completed April 29, 2026, 3:23 a.m.
Created at: April 17, 2026, 3:23 p.m.