Triple

T12913846
Position Surface form Disambiguated ID Type / Status
Subject Piipaash language E308926 entity
Predicate alternativeName P39 FINISHED
Object Piipáash E63688 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: Piipáash | Statement: [Piipaash language, alternativeName, Piipáash]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Piipáash
Context triple: [Piipaash language, alternativeName, Piipáash]
  • A. Piipaash chosen
    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.
  • B. Piikani
    Piikani are an Indigenous people of the Blackfoot Confederacy traditionally based in the northern Great Plains of North America.
  • C. Tappara
    Tappara is a prominent professional ice hockey club from Tampere, Finland, known as one of the most successful and historic teams in the Finnish Liiga.
  • D. 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.
  • 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_69d7bdf92b588190acdf2a2291ac4590 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d971a0d6508190bca9668e9e06abfe completed April 10, 2026, 9:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6c0e7e9fc8190ad065a587c6c45dd completed May 3, 2026, 3:28 a.m.
Created at: April 9, 2026, 5:41 p.m.