Triple

T19892269
Position Surface form Disambiguated ID Type / Status
Subject Hopkins, Missouri E478059 entity
Predicate isPartOfCountySeatRegion P14649 FINISHED
Object Nodaway County, Missouri NE NERFINISHED

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: Nodaway County, Missouri | Statement: [Hopkins, Missouri, isPartOfCountySeatRegion, Nodaway County, Missouri]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isPartOfCountySeatRegion
Context triple: [Hopkins, Missouri, isPartOfCountySeatRegion, Nodaway County, Missouri]
  • A. inCountySeatRegionOf
    Indicates that a county seat is located within and serves as the administrative center for a specified region.
  • B. isInCountySeatOf chosen
    Indicates that one entity is located within the town or city that serves as the administrative center (county seat) of a specified county.
  • C. hasCountySeatRelation
    Indicates that a specific place serves as the county seat (administrative center) of a particular county.
  • D. hasCountySeatWithin
    Indicates that the designated county’s official administrative center (county seat) is located within the specified geographic area or boundary.
  • E. hasCountySeatOf
    Indicates that a place serves as the administrative county seat (capital) of a specified county.
  • F. None of above.

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_69d8e51f32b08190b3687f4f60353250 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6590ed7988190bc6b610d1f4fa194 completed April 20, 2026, 4:49 p.m.
PD Predicate disambiguation batch_69e537ecda248190895c96afb6243823 completed April 19, 2026, 8:15 p.m.
Created at: April 10, 2026, 1:52 p.m.