Triple

T7762123
Position Surface form Disambiguated ID Type / Status
Subject Indianapolis metropolitan area E176047 entity
Predicate hasPrincipalCity P3940 FINISHED
Object Zionsville E599837 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: Zionsville | Statement: [Indianapolis metropolitan area, hasPrincipalCity, Zionsville]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zionsville
Context triple: [Indianapolis metropolitan area, hasPrincipalCity, Zionsville]
  • A. Zionsville chosen
    Zionsville is a suburban town in Boone County, Indiana, known for its brick-paved Main Street and affluent residential character northwest of Indianapolis.
  • B. Brownsburg
    Brownsburg is a suburban town in central Indiana that serves as a growing residential and commercial community within the greater Indianapolis area.
  • C. Beech Grove
    Beech Grove is a small, independent city located within the Indianapolis metropolitan area in central Indiana.
  • D. Kendallville
    Kendallville is a small city in Noble County, Indiana, known for its historic downtown, local lakes, and role as a regional hub in northeastern Indiana.
  • E. McCordsville
    McCordsville is a growing suburban town in Hancock County, Indiana, known for its residential communities and proximity to Indianapolis.
  • 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_69c69962923c8190ac74d28b4f9fe0a0 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c70404c2108190ad2b900ac9bf582b completed March 27, 2026, 10:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69c9116b86cc8190997077243f99cc7d completed March 29, 2026, 11:47 a.m.
Created at: March 27, 2026, 4:09 p.m.