Triple
T7440874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kawki |
E171747
|
entity |
| Predicate | alternativeName |
P39
|
FINISHED |
| Object | Cauque |
E171747
|
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: Cauque | Statement: [Kawki, alternativeName, Cauque]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cauque Context triple: [Kawki, alternativeName, Cauque]
-
A.
Cauque
chosen
Cauque is an alternative name for Kawki, a highly endangered Quechuan language spoken by a small indigenous community in Peru.
-
B.
Cauqui
Cauqui is an indigenous Aymaran language variety spoken by a small community in the Andean region of Peru.
-
C.
Guaro
Guaro is a small locality within Cueto Municipality, likely a rural community in a Spanish-speaking region.
-
D.
Jucuna
Jucuna is an alternative name for the Yucuna language, an indigenous Arawakan language spoken in the Amazon region of Colombia.
-
E.
Cáqueza
Cáqueza is a small municipality and town in the Andean region of central Colombia, known for its rural landscapes and proximity to Bogotá in the department of Cundinamarca.
- 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_69c68a64228c8190affaec2a8127ce7b |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f34d84008190936af2b3670ef210 |
completed | March 27, 2026, 9:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c827976b9081909ac722b397ae0d97 |
completed | March 28, 2026, 7:10 p.m. |
Created at: March 27, 2026, 3:13 p.m.