Triple

T21544321
Position Surface form Disambiguated ID Type / Status
Subject Curarén E531578 entity
Predicate usesCurrency P188 FINISHED
Object Honduran lempira 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: Honduran lempira | Statement: [Curarén, usesCurrency, Honduran lempira]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Honduran lempira
Context triple: [Curarén, usesCurrency, Honduran lempira]
  • A. Honduran lempira chosen
    The Honduran lempira is the official national currency of Honduras, named after an indigenous Lenca leader who resisted Spanish conquest.
  • B. Coconuco
    Coconuco is an indigenous language of Colombia belonging to the Barbacoan language family.
  • C. Haban
    Haban is a historic town in eastern Yemen that once served as the political and commercial center of the Wahidi Sultanates in the Hadhramaut region.
  • D. Yucpa
    Yucpa is an indigenous language spoken by the Yukpa people of the Sierra de Perijá region along the Colombia–Venezuela border.
  • E. Carazo
    Carazo is a department in southwestern Nicaragua known for its agricultural production and proximity to the Pacific coast.
  • 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_69e0c45f17148190949c330ab9c27706 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eeb58d66ec8190b654a46932c841d3 completed April 27, 2026, 1:02 a.m.
Created at: April 16, 2026, 6:28 p.m.