Triple

T11182200
Position Surface form Disambiguated ID Type / Status
Subject Piikani Nation E264567 entity
Predicate usesEndonym P1435 FINISHED
Object Piikani E910119 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: Piikani | Statement: [Piikani Nation, usesEndonym, Piikani]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Piikani
Context triple: [Piikani Nation, usesEndonym, Piikani]
  • A. Piikani chosen
    Piikani are an Indigenous people of the Blackfoot Confederacy traditionally based in the northern Great Plains of North America.
  • B. Pioppi
    Pioppi is a small coastal village in southern Italy’s Cilento region, known for its traditional Mediterranean lifestyle and as a key site in the study of the Mediterranean diet.
  • C. Pipikoro
    Pipikoro is an Austronesian language spoken in Central Sulawesi, Indonesia, known locally as an alternate name for the Uma language.
  • D. Piipaash
    Piipaash are a Native American people of the lower Colorado River region, closely related to the Maricopa and known for their distinct language and cultural traditions.
  • E. Pikaliiva
    Pikaliiva is a residential subdistrict of Tallinn, Estonia, located within the Haabersti district.
  • 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_69d6aa9dafac8190bd90d2c74f661aa7 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8a7f35481909f35feb94ef10e80 completed April 9, 2026, 5:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69e496e47f688190b2e8bc71605f9db3 completed April 19, 2026, 8:48 a.m.
Created at: April 8, 2026, 9:29 p.m.