Triple
T16951832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qʼeqchiʼ |
E411196
|
entity |
| Predicate | hasDialect |
P4251
|
FINISHED |
| Object | Lanquin Qʼeqchiʼ |
E1197173
|
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: Lanquin Qʼeqchiʼ | Statement: [Qʼeqchiʼ, hasDialect, Lanquin Qʼeqchiʼ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lanquin Qʼeqchiʼ Context triple: [Qʼeqchiʼ, hasDialect, Lanquin Qʼeqchiʼ]
-
A.
Cahabón Qʼeqchiʼ
Cahabón Qʼeqchiʼ is a regional variety of the Qʼeqchiʼ Mayan language spoken primarily in and around the Cahabón area of Guatemala.
-
B.
Tlaltenango
Tlaltenango is a municipality and urban locality that forms part of the greater Puebla metropolitan region in central Mexico.
-
C.
Curaray Kichwa
Curaray Kichwa is a regional variety of the Kichwa language spoken by Indigenous communities in the Curaray River area of the Ecuadorian Amazon.
-
D.
Lanquin
chosen
Lanquin is a small town in Guatemala’s Alta Verapaz region, known as a gateway to the Semuc Champey natural pools and surrounding cave systems.
-
E.
Huamanga
Huamanga is the historical name of the Peruvian city now known as Ayacucho, renowned for its colonial architecture and role in the country’s independence history.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0197f308190af7185fc9cc7a6e9 |
completed | April 18, 2026, 6:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a011b3d9c648190bd0437c2f1e19b41 |
completed | May 10, 2026, 11:56 p.m. |
Created at: April 10, 2026, 5:31 a.m.