Triple

T18802790
Position Surface form Disambiguated ID Type / Status
Subject Cuyonon E459797 entity
Predicate hasAlternateName P39 FINISHED
Object Cuyoño 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: Cuyoño | Statement: [Cuyonon, hasAlternateName, Cuyoño]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cuyoño
Context triple: [Cuyonon, hasAlternateName, Cuyoño]
  • A. Cuyoño chosen
    Cuyoño is an Austronesian language spoken primarily in the Cuyo Islands and parts of Palawan in the Philippines.
  • B. Cuyocuyo
    Cuyocuyo is a rural town and district in the highlands of southeastern Peru, known for its Andean landscapes and traditional Quechua-speaking communities.
  • C. Ituni
    Ituni is a small inland community in Guyana located between the towns of Linden and Kwakwani, historically associated with logging and bauxite-related activities.
  • D. Lumbaquí
    Lumbaquí is a small town in northeastern Ecuador that serves as a local hub within the Amazonian Sucumbíos Province.
  • E. Machalí
    Machalí is a Chilean city in the O'Higgins Region known for its proximity to the El Teniente copper mine and the Andean foothills.
  • 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_69d8d398c7d4819091cb2f7e48948aeb completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5a0253f748190998995e3b1524357 completed April 20, 2026, 3:40 a.m.
Created at: April 10, 2026, 11:53 a.m.