Triple
T180447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quechua |
E3862
|
entity |
| Predicate | hasDialect |
P4251
|
FINISHED |
| Object | Kichwa |
E6374
|
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: Kichwa | Statement: [Quechua, hasDialect, Kichwa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kichwa Context triple: [Quechua, hasDialect, Kichwa]
-
A.
Kichwa
chosen
Kichwa is a Quechuan indigenous language variety widely spoken by Andean communities in Ecuador and neighboring regions.
-
B.
Pichi language
Pichi is an English-based creole language spoken primarily in Equatorial Guinea, where it serves as a major lingua franca and has significantly shaped local varieties of Spanish.
-
C.
Chemehuevi language
Chemehuevi language is a critically endangered Uto-Aztecan language traditionally spoken by the Chemehuevi people of the Great Basin region in the southwestern United States.
-
D.
Ipai language
The Ipai language is a Native American language traditionally spoken by the Kumeyaay (Ipai) people of southern California and northern Baja California.
-
E.
Aymara
Aymara is an indigenous language spoken primarily by the Aymara people of the central Andes in countries such as Bolivia, Peru, and Chile.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25bafd5808190a0a0cb2b21ce007f |
completed | Feb. 28, 2026, 3:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a2fd0405608190bf4c1aa8a8fa9ad1 |
completed | Feb. 28, 2026, 2:34 p.m. |
Created at: Feb. 28, 2026, 2:40 a.m.