Triple

T20476247
Position Surface form Disambiguated ID Type / Status
Subject Wampis E502324 entity
Predicate hasAlternativeName P39 FINISHED
Object Huambisa 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: Huambisa | Statement: [Wampis, hasAlternativeName, Huambisa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Huambisa
Context triple: [Wampis, hasAlternativeName, Huambisa]
  • A. Huambisa chosen
    Huambisa is an indigenous Jivaroan language spoken by the Huambisa people of the northern Peruvian Amazon.
  • B. Huancané
    Huancané is a town in southern Peru that serves as an administrative and commercial center in the Puno region near Lake Titicaca.
  • C. Chimbay
    Chimbay is a town in the autonomous Republic of Karakalpakstan in northwestern Uzbekistan, serving as a local administrative and economic center in the region.
  • D. Ouahigouya
    Ouahigouya is a major city in northern Burkina Faso known as an important commercial and administrative center of the region.
  • E. Hualañé
    Hualañé is a rural Chilean town and commune in the Maule Region, known for its agricultural activities and location near the Mataquito River.
  • 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_69e0b4af32848190aea80682b44d5d6e completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6996584648190a1a6dfcb57782b7f completed April 20, 2026, 9:23 p.m.
Created at: April 16, 2026, 11:34 a.m.