Triple

T11437598
Position Surface form Disambiguated ID Type / Status
Subject Putumayo E271049 entity
Predicate capital P234 FINISHED
Object Mocoa E727845 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: Mocoa | Statement: [Putumayo, capital, Mocoa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mocoa
Context triple: [Putumayo, capital, Mocoa]
  • A. Mocoa chosen
    Mocoa is a small city in southwestern Colombia, known as the administrative and commercial center of the Putumayo region and as a gateway to the Amazon foothills.
  • B. Tumaco
    Tumaco is a coastal city and municipality in southwestern Colombia, known for its Afro-Colombian culture, Pacific beaches, and rich pre-Hispanic goldworking heritage.
  • C. Soacha
    Soacha is a rapidly growing industrial and residential city in central Colombia, located just southwest of Bogotá in the department of Cundinamarca.
  • D. Yopal
    Yopal is a city in eastern Colombia that serves as the main urban and economic center of the Llanos (plains) region in the Casanare Department.
  • E. Sogamoso
    Sogamoso is a Colombian city in the Andean region known historically as a major religious and cultural center of the Muisca civilization and today for its industry and mining.
  • 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_69d6aadeef688190874bcecd88b3dd9b completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8088711ec8190afae9f4d9f2a11ca completed April 9, 2026, 8:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69e5d38727fc8190b5daac83e03491e6 completed April 20, 2026, 7:19 a.m.
Created at: April 8, 2026, 9:35 p.m.