Triple

T21851321
Position Surface form Disambiguated ID Type / Status
Subject Pukina E539510 entity
Predicate hasAlternativeName P39 FINISHED
Object Puquina NE NERFINISHED

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: Puquina | Statement: [Pukina, hasAlternativeName, Puquina]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Puquina
Context triple: [Pukina, hasAlternativeName, Puquina]
  • A. Puquina chosen
    Puquina is an extinct and poorly documented indigenous language once spoken in the Andean region of South America, particularly around Lake Titicaca.
  • B. Pichasca
    Pichasca is a small settlement in Chile known for its proximity to the Hurtado River and the surrounding Andean landscapes.
  • C. Coyolito
    Coyolito is a small coastal village in southern Honduras known as a gateway to the beaches and fishing spots around Zacate Grande Island in the Gulf of Fonseca.
  • D. Pundaquit
    Pundaquit is a coastal barangay in San Antonio, Zambales, Philippines, known for its beaches, surfing spots, and as a jump-off point to nearby islands like Capones and Anawangin.
  • E. Curipata
    Curipata is a small rural settlement located in Peru's central highland region within Yauli Province.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c476c3c88190a92d08ebb59a128a completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f0bd5904108190af67609a9ab8616e completed April 28, 2026, 1:59 p.m.
Created at: April 16, 2026, 6:56 p.m.