Triple
T9542380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teke |
E230188
|
entity |
| Predicate | ethnonym |
P4709
|
FINISHED |
| Object | Teke |
E240267
|
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: [Teke, ethnonym, Teke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Teke Context triple: [Teke, ethnonym, Teke]
-
A.
Teke
chosen
Teke is a Bantu language spoken primarily in the Republic of the Congo and neighboring Central African regions by the Teke people.
-
B.
Teke
Teke are a prominent Turkmen tribal group historically known for their influence in Central Asia and their famed Akhal-Teke horses.
-
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.
Teckberg
Teckberg is a prominent hill in the Swabian Jura of Baden-Württemberg, Germany, best known as the site of the historic Teck Castle overlooking the surrounding region.
- 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_69ca847c70b8819088a0a0bad64a50d6 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98e82bb08190aed3ed0627923d22 |
completed | April 1, 2026, 10:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d14c6538b08190a9f81304214a876d |
completed | April 4, 2026, 5:37 p.m. |
Created at: March 30, 2026, 8:01 p.m.