Triple

T9840701
Position Surface form Disambiguated ID Type / Status
Subject Eastern Dakota E239215 entity
Predicate modernPopulationCenters P90280 FINISHED
Object Minnesota reservations LITERAL 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: Minnesota reservations | Statement: [Eastern Dakota, modernPopulationCenters, Minnesota reservations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: modernPopulationCenters
Context triple: [Eastern Dakota, modernPopulationCenters, Minnesota reservations]
  • A. majorPopulationCenter
    Indicates that a location functions as a primary hub of population concentration and activity within a region.
  • B. populationFocus
    Indicates that something is primarily directed toward, concerned with, or designed for a particular population or demographic group.
  • C. majorPopulationIn
    Indicates that a significant portion of a population is located in or primarily associated with a particular place or region.
  • D. hasPopulationCenter
    Indicates that an area, region, or administrative unit contains or is served by a primary settlement or population hub.
  • E. populationConcentration
    Indicates the degree to which a population is densely gathered or distributed within a specific area or region.
  • F. None of above. chosen

Provenance (4 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_69ca84e3f0c48190ada72a65ebd50efd completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb34c920c81909b56ed9936b15f9b completed April 2, 2026, 12:07 a.m.
PD Predicate disambiguation batch_69cd03e30bc08190816c0a6d29c21b0f completed April 1, 2026, 11:39 a.m.
PDg Predicate description generation batch_69cd06abc9248190a506b64e9c516d03 completed April 1, 2026, 11:51 a.m.
Created at: March 30, 2026, 8:33 p.m.