Triple

T22192409
Position Surface form Disambiguated ID Type / Status
Subject Javeriano Moxeño E548460 entity
Predicate hasAutonymLanguage P70102 FINISHED
Object Moxeñ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: Moxeño | Statement: [Javeriano Moxeño, hasAutonymLanguage, Moxeño]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moxeño
Context triple: [Javeriano Moxeño, hasAutonymLanguage, Moxeño]
  • A. Moxeño chosen
    Moxeño is an indigenous Arawakan language spoken by the Moxeño people of Bolivia’s Beni region.
  • B. Carvallo
    Carvallo is a surname, likely a variant of Carvajal, found in Spanish- and Portuguese-speaking regions.
  • C. El Cuy
    El Cuy is a small town in the Río Negro Province of Argentina that serves as the administrative center of the surrounding El Cuy Department.
  • D. Mazama bororo
    Mazama bororo, commonly known as the small red brocket deer, is a rare and little-known deer species endemic to the Atlantic Forest of southeastern Brazil.
  • E. Cuyón
    Cuyón is a rural barrio (district) of the municipality of Aibonito in central Puerto Rico, known for its mountainous terrain and agricultural character.
  • 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_69e11e3e0c7c8190b30d278845e2497e completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12ae49ec881908fa42446b19e3f2d completed April 28, 2026, 9:47 p.m.
Created at: April 16, 2026, 8:35 p.m.