Triple
T7762326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karanga |
E176053
|
entity |
| Predicate | mutuallyIntelligibleWith |
P7448
|
FINISHED |
| Object | Manyika |
E153635
|
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: Manyika | Statement: [Karanga, mutuallyIntelligibleWith, Manyika]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Manyika Context triple: [Karanga, mutuallyIntelligibleWith, Manyika]
-
A.
Manyika
chosen
Manyika is a major dialect of the Shona language spoken primarily in eastern Zimbabwe and adjacent areas of Mozambique.
-
B.
Muchik
Muchik is an extinct indigenous language once spoken by the Mochica people along Peru’s northern coast.
-
C.
Muyil
Muyil is an ancient Maya archaeological site in Mexico’s Yucatán Peninsula, known for its well-preserved temples and proximity to the Sian Ka'an Biosphere Reserve.
-
D.
Mille
Mille is a French surname most notably borne by individuals such as Stéphane Mille.
-
E.
Milyan
Milyan is an extinct Anatolian Indo-European language once spoken in southwestern Asia Minor, known primarily from a small corpus of inscriptions.
- 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_69c69962923c8190ac74d28b4f9fe0a0 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70404c2108190ad2b900ac9bf582b |
completed | March 27, 2026, 10:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8c7d658888190af97b83127086a2b |
completed | March 29, 2026, 6:33 a.m. |
Created at: March 27, 2026, 4:09 p.m.