Triple

T1174512
Position Surface form Disambiguated ID Type / Status
Subject Miller’s Hollow E24987 entity
Predicate followedBy P78 FINISHED
Object Kanesville E3838 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: Kanesville | Statement: [Miller’s Hollow, followedBy, Kanesville]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kanesville
Context triple: [Miller’s Hollow, followedBy, Kanesville]
  • A. Kanesville chosen
    Kanesville was the mid-19th-century Mormon settlement that later became the city of Council Bluffs, Iowa.
  • B. Juneautown
    Juneautown was one of the original 19th-century settlements that later became part of the city of Milwaukee, Wisconsin.
  • C. Parkville
    Parkville is a suburban community in Maryland, United States, located just northeast of Baltimore City.
  • D. Youngsville
    Youngsville is a small town in Franklin County, North Carolina, located just north of the Raleigh–Durham metropolitan area.
  • E. Kingsburg
    Kingsburg is a small, historically Swedish-themed city in California’s San Joaquin Valley known for its agricultural community and distinctive Scandinavian character.
  • 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_69a494082a7c819095004f423f294a64 completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bcee38c881909c2fc73ba35f7253 completed March 1, 2026, 10:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac93b6343c8190af6e28ccdaab6562 completed March 7, 2026, 9:08 p.m.
Created at: March 1, 2026, 7:45 p.m.