Triple

T13980649
Position Surface form Disambiguated ID Type / Status
Subject Kamayo E336299 entity
Predicate hasAlternativeName P39 FINISHED
Object Kamayó E336299 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: Kamayó | Statement: [Kamayo, hasAlternativeName, Kamayó]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kamayó
Context triple: [Kamayo, hasAlternativeName, Kamayó]
  • A. Kamayo chosen
    Kamayo is an Austronesian language spoken primarily in parts of Mindanao in the Philippines, particularly in the Caraga region.
  • B. Acawayo
    Acawayo is an alternative name for the Akawaio language, an indigenous Cariban language spoken by the Akawaio people of northern South America.
  • C. Pacasmayo
    Pacasmayo is a coastal city in northern Peru known for its long pier, surfing beaches, and colonial-era architecture.
  • D. Tayasal
    Tayasal was a major Itza Maya city in present-day Guatemala that served as one of the last independent Maya strongholds before Spanish conquest.
  • E. Kaxuyana
    Kaxuyana is an indigenous language variety spoken by the Kaxuyana people of northern Brazil, closely related to other Cariban languages of the region.
  • 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_69d81c639e808190a0e4b4f3d31c6a59 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2ea10dc88190b9720919a021e570 completed April 14, 2026, 12:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69fbc323d8ac81909b4eaf44f8fd462c completed May 6, 2026, 10:39 p.m.
Created at: April 9, 2026, 10:18 p.m.