Triple
T8600691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamahaq |
E203665
|
entity |
| Predicate | hasAlternativeTransliteration |
P5923
|
FINISHED |
| Object | Tamahaq |
E203665
|
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: Tamahaq | Statement: [Tamahaq, hasAlternativeTransliteration, Tamahaq]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tamahaq Context triple: [Tamahaq, hasAlternativeTransliteration, Tamahaq]
-
A.
Tamahaq
chosen
Tamahaq is a Berber (Amazigh) language traditionally spoken by the Tuareg people of the central Sahara.
-
B.
Tamana
Tamana is one of the southernmost coral atolls of Kiribati, known for its small size, traditional I-Kiribati culture, and remote Pacific Ocean location.
-
C.
Muribenua
Muribenua is a village on the low-lying coral atoll of Nikunau in the Republic of Kiribati, a Pacific island nation.
-
D.
Tayshet
Tayshet is a town in Irkutsk Oblast, Russia, known as a major railway junction in Siberia.
-
E.
Tanasi
Tanasi was a historic Overhill Cherokee town in present-day Tennessee that gave the state its name and served as an early political center for the Cherokee.
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46d8ff408190acc7cd8dc99b2689 |
completed | March 31, 2026, 10:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cea8e903d0819095bfa87b83c3599f |
completed | April 2, 2026, 5:35 p.m. |
Created at: March 30, 2026, 6:24 p.m.