Triple
T7720011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jopara |
E174983
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Yopará |
E174983
|
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: Yopará | Statement: [Jopara, hasAlternativeName, Yopará]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yopará Context triple: [Jopara, hasAlternativeName, Yopará]
-
A.
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.
-
B.
Pasochoa
Pasochoa is an extinct volcanic mountain in Ecuador known for its lush cloud forests and rich biodiversity within a protected ecological reserve.
-
C.
Jopara
chosen
Jopara is a mixed language spoken in Paraguay that blends Guaraní and Spanish in everyday communication.
-
D.
Yawal
Yawal is a town in the Indian state of Maharashtra, situated in the Jalgaon district and known for its agricultural surroundings and local markets.
-
E.
Pacasmayo
Pacasmayo is a coastal city in northern Peru known for its long pier, surfing beaches, and colonial-era architecture.
- 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_69c6995d541c81909eaa646b1a8369a9 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702eedc088190be645c029dfc462a |
completed | March 27, 2026, 10:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8b513f7d481908d2ce64d9685289c |
completed | March 29, 2026, 5:13 a.m. |
Created at: March 27, 2026, 4:05 p.m.