Triple

T8853844
Position Surface form Disambiguated ID Type / Status
Subject Dakota Territory E210702 entity
Predicate capital P234 FINISHED
Object Yankton E447486 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: Yankton | Statement: [Dakota Territory, capital, Yankton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yankton
Context triple: [Dakota Territory, capital, Yankton]
  • A. Yankton chosen
    Yankton are a Native American group that forms one of the principal divisions of the Dakota (Sioux) people, traditionally living in the Upper Midwest region of the United States.
  • B. Mandan
    The Mandan are a Native American tribe of the Northern Plains, historically known as semi-sedentary village farmers and traders along the upper Missouri River in present-day North Dakota.
  • C. Madison, South Dakota
    Madison, South Dakota is a small city in eastern South Dakota known as a regional hub for education, technology, and agriculture.
  • D. Columbia, South Dakota
    Columbia, South Dakota is a small rural town located in northeastern South Dakota within Brown County.
  • E. Hudson, South Dakota
    Hudson, South Dakota is a small rural town located in southeastern South Dakota near the Iowa border.
  • 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_69ca838a424c8190b1ecac115c2927e7 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc60c6dce88190b175698b191fb89b completed April 1, 2026, 12:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfa09557dc81908b5690bf5c392528 completed April 3, 2026, 11:12 a.m.
Created at: March 30, 2026, 6:49 p.m.