Triple
T13424988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | southern Turkmenistan |
E313456
|
entity |
| Predicate | ethnicGroup |
P194
|
FINISHED |
| Object | Teke |
E230188
|
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: Teke | Statement: [southern Turkmenistan, ethnicGroup, Teke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Teke Context triple: [southern Turkmenistan, ethnicGroup, Teke]
-
A.
Teke
chosen
Teke are a prominent Turkmen tribal group historically known for their influence in Central Asia and their famed Akhal-Teke horses.
-
B.
Teke
Teke is a Bantu language spoken primarily in the Republic of the Congo and neighboring Central African regions by the Teke people.
-
C.
Teok
Teok is a town in the Jorhat district of Assam, India, known as a local commercial and transportation hub in the region.
-
D.
Tektitek
Tektitek is a Mayan language spoken primarily by the Tektiteko people in parts of Guatemala and Mexico.
-
E.
Tekoa
Tekoa is an Israeli settlement and community in the Gush Etzion region of the West Bank, known for its mixed religious-secular population and proximity to Jerusalem.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed066408190a416880affd8416e |
completed | April 12, 2026, 2:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7398984f48190adaa1963d261d538 |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 9, 2026, 9:39 p.m.