Triple
T7185841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villa de Leyva |
E167568
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Ráquira |
E174740
|
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: Ráquira | Statement: [Villa de Leyva, near, Ráquira]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ráquira Context triple: [Villa de Leyva, near, Ráquira]
-
A.
Ráquira
chosen
Ráquira is a Colombian town renowned for its traditional pottery, colorful handicrafts, and vibrant colonial architecture.
-
B.
Rauco
Rauco is a rural municipality and commune in central Chile’s Maule Region, known for its agricultural activities and proximity to the city of Curicó.
-
C.
Coruripe
Coruripe is a coastal municipality in northeastern Brazil known for its beaches, fishing activities, and sugarcane agriculture.
-
D.
Maraita
Maraita is a small municipality located in the Francisco Morazán Department of central Honduras.
-
E.
Tupiza
Tupiza is a small historic town in southern Bolivia known for its dramatic red-rock canyons and as a gateway to Andean landscapes and mining regions.
- 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_69c6888a7c548190a3d39b52a393080f |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e8df6a6881909c3174f86c9a6b28 |
completed | March 27, 2026, 8:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7d37cfb8c8190a788dcaa1080fb0b |
completed | March 28, 2026, 1:11 p.m. |
Created at: March 27, 2026, 2:49 p.m.