Triple

T29363013
Position Surface form Disambiguated ID Type / Status
Subject Adair County, Oklahoma E744641 entity
Predicate hasSignificantCherokeePopulation P1898 FINISHED
Object Yes 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: Yes | Statement: [Adair County, Oklahoma, hasSignificantCherokeePopulation, Yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSignificantCherokeePopulation
Context triple: [Adair County, Oklahoma, hasSignificantCherokeePopulation, Yes]
  • A. consideredByManyCherokee
    Indicates that something is regarded or believed by many Cherokee people in a particular way.
  • B. containsNativeAmericanTribe
    Indicates that one entity geographically or administratively includes the presence, territory, or jurisdiction of a Native American tribe.
  • C. hasSignificantPopulationGroup chosen
    Indicates that an entity contains or is associated with a notable or substantial subgroup of a population, distinguished by shared characteristics or attributes.
  • D. hasMajorityIndigenousPopulation
    Indicates that the majority of the population in a given area or group is composed of Indigenous peoples.
  • E. isCherokeeNameFor
    Indicates that one term is the Cherokee-language name used to refer to another entity.
  • 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_69f0a79aee588190b490f19d93c6e52d completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69f7764ab1fc81909f9348db87bd7692 completed May 3, 2026, 4:22 p.m.
PD Predicate disambiguation batch_69f76905d9c88190b1ee810bc9ab644f completed May 3, 2026, 3:25 p.m.
Created at: April 28, 2026, 2:20 p.m.