Triple

T10818792
Position Surface form Disambiguated ID Type / Status
Subject Boone County, Indiana E255304 entity
Predicate containsSettlement P847 FINISHED
Object Ulen, Indiana E562540 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: Ulen, Indiana | Statement: [Boone County, Indiana, containsSettlement, Ulen, Indiana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ulen, Indiana
Context triple: [Boone County, Indiana, containsSettlement, 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. Apalona, Indiana
    Apalona, Indiana is an unincorporated rural community located in Perry County in the southern part of the state.
  • C. Majenica, Indiana
    Majenica, Indiana is an unincorporated rural community located in Huntington County in the U.S. state of Indiana.
  • D. Cunot, Indiana
    Cunot, Indiana is an unincorporated rural community located in Owen County in the U.S. state of Indiana.
  • E. Schley, Indiana
    Schley, Indiana is an unincorporated community located in Perry County in the southern part of the U.S. state of Indiana.
  • 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_69d6aa8081448190a9324184f2bd1c26 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d7344866f88190be4addb7c8020fce completed April 9, 2026, 5:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69de8569178481909474e939a3e4c217 completed April 14, 2026, 6:20 p.m.
Created at: April 8, 2026, 9:18 p.m.