Triple

T6777095
Position Surface form Disambiguated ID Type / Status
Subject Palikur language E155584 entity
Predicate hasAlternativeName P39 FINISHED
Object Parikwene E618327 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: Parikwene | Statement: [Palikur language, hasAlternativeName, Parikwene]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Parikwene
Context triple: [Palikur language, hasAlternativeName, Parikwene]
  • A. Parikwaki chosen
    Parikwaki is an alternative name for the Palikur language, an indigenous language spoken by the Palikur people of the Amazon region in Brazil and French Guiana.
  • B. Pucikwar
    Pucikwar is an extinct Great Andamanese language once spoken by the Pucikwar people of the Andaman Islands in India.
  • C. Kulisusu
    Kulisusu is a town and administrative center located in the province of Southeast Sulawesi, Indonesia.
  • D. Pipikoro
    Pipikoro is an Austronesian language spoken in Central Sulawesi, Indonesia, known locally as an alternate name for the Uma language.
  • E. Pitiüses
    The Pitiüses are a small Mediterranean archipelago comprising the Spanish Balearic Islands of Ibiza and Formentera and their surrounding islets.
  • 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_69c688162bf8819088b664b5c3b5be7a completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d26725208190b64935cfd08b2aff completed March 27, 2026, 6:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69c71a8263508190ad5cace74d7d7ac2 completed March 28, 2026, 12:02 a.m.
Created at: March 27, 2026, 2:13 p.m.