Triple

T5734163
Position Surface form Disambiguated ID Type / Status
Subject Moche Valley E126457 entity
Predicate languageHistoricallySpoken P1434 FINISHED
Object Mochica language E128096 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: Mochica language | Statement: [Moche Valley, languageHistoricallySpoken, Mochica language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mochica language
Context triple: [Moche Valley, languageHistoricallySpoken, Mochica language]
  • A. Mochica language chosen
    The Mochica language is an extinct pre-Columbian language once spoken on the northern coast of Peru, associated with the Moche (Mochica) civilization.
  • B. Yaneshaʼ language
    Yaneshaʼ language is an Arawakan indigenous language spoken by the Yaneshaʼ people in the central Peruvian Amazon.
  • C. Piapoco language
    The Piapoco language is an indigenous Arawakan language spoken by the Piapoco people of Colombia and Venezuela.
  • D. Yucuna language
    The Yucuna language is an indigenous Arawakan language spoken by the Yucuna people of the Colombian Amazon.
  • E. Amuzgo language
    Amuzgo language is an indigenous Oto-Manguean language spoken primarily by the Amuzgo people in the states of Guerrero and Oaxaca in southern Mexico.
  • 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_69c0083082288190b7478cead6b5430a completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c02536706c8190a69665b75c8a38e9 completed March 22, 2026, 5:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c05a931b3c819092119a1587625eb5 completed March 22, 2026, 9:09 p.m.
Created at: March 22, 2026, 3:47 p.m.