Triple

T7677539
Position Surface form Disambiguated ID Type / Status
Subject Marquette E173898 entity
Predicate hasToponymicUse P20238 FINISHED
Object Marquette, Kansas E690573 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: Marquette, Kansas | Statement: [Marquette, hasToponymicUse, Marquette, Kansas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Marquette, Kansas
Context triple: [Marquette, hasToponymicUse, Marquette, Kansas]
  • A. Marquette, Kansas chosen
    Marquette, Kansas is a small rural city in central Kansas known for its historic downtown and proximity to the Smoky Valley scenic area.
  • B. St. Marys, Kansas
    St. Marys, Kansas is a small city in northeastern Kansas known for its historic Catholic institutions and traditional community character.
  • C. Kimball, Kansas
    Kimball, Kansas is a small unincorporated community located in Neosho County in southeastern Kansas.
  • D. Mayetta, Kansas
    Mayetta, Kansas is a small city in northeastern Kansas that serves as the governmental center of the Prairie Band Potawatomi Nation.
  • E. Belvue, Kansas
    Belvue, Kansas is a small rural city in Pottawatomie County that functions as part of the greater Manhattan, Kansas regional community.
  • 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_69c6995703e0819081de77361b602e78 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c701fbb4788190adf1e2d39be358c1 completed March 27, 2026, 10:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69c998ad1ee08190bbde7900f1bb34bf completed March 29, 2026, 9:25 p.m.
Created at: March 27, 2026, 4:01 p.m.