Triple

T7250838
Position Surface form Disambiguated ID Type / Status
Subject Asháninka language E157595 entity
Predicate alternativeName P39 FINISHED
Object Campa E265767 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: Campa | Statement: [Asháninka language, alternativeName, Campa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Campa
Context triple: [Asháninka language, alternativeName, Campa]
  • A. Chinandega
    Chinandega is a city in northwestern Nicaragua known as a commercial and agricultural hub near the country’s highest volcanoes.
  • B. Guarequena
    Guarequena is an alternative name for the Warekena language, an indigenous Arawakan language spoken in parts of Brazil and Venezuela.
  • C. Supía
    Supía is a municipality in the Caldas Department of Colombia, known historically for gold mining and its indigenous Emberá Chamí heritage.
  • D. Huambisa chosen
    Huambisa is an indigenous Jivaroan language spoken by the Huambisa people of the northern Peruvian Amazon.
  • E. Pomerape
    Pomerape is a stratovolcano in the Andes Mountains on the border between Chile and Bolivia, known as part of the Nevados de Payachata volcanic group.
  • 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_69c6882d81d4819085f7ff862951ee4f completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6ea791fec8190aee56ab4503770be completed March 27, 2026, 8:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7d3a7502081909d2a97a60cc445ae completed March 28, 2026, 1:12 p.m.
Created at: March 27, 2026, 2:56 p.m.