Triple

T2686283
Position Surface form Disambiguated ID Type / Status
Subject Shawnee E57491 entity
Predicate subgroup P10 FINISHED
Object Piqua E186332 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: Piqua | Statement: [Shawnee, subgroup, Piqua]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Piqua
Context triple: [Shawnee, subgroup, Piqua]
  • A. Piqua, Ohio chosen
    Piqua, Ohio is a small city in western Ohio known for its historic downtown, manufacturing heritage, and location along the Great Miami River.
  • B. Menifee
    Menifee is a rapidly growing suburban city in Southern California known for its residential communities and proximity to major Inland Empire urban centers.
  • C. Paynesville
    Paynesville is a major city in Liberia, located near the capital Monrovia and known for its role as a key urban and sporting center in the country.
  • D. Fort Dodge
    Fort Dodge is a historic 19th-century U.S. Army post in Kansas that served as a key military outpost protecting travelers and trade along the Santa Fe Trail.
  • E. Kanesville
    Kanesville was the mid-19th-century Mormon settlement that later became the city of Council Bluffs, Iowa.
  • 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_69ab4a5028388190a36f3baf1588309e completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd9ef2fe0819082bbe746ca682a7e completed March 7, 2026, 7:55 a.m.
NED1 Entity disambiguation (via context triple) batch_69afa07228088190bb4942b3a25c938b completed March 10, 2026, 4:39 a.m.
Created at: March 6, 2026, 9:54 p.m.