Triple
T11458605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shabo people |
E271591
|
entity |
| Predicate | ethnonym |
P4709
|
FINISHED |
| Object | Shabo |
E247378
|
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: Shabo | Statement: [Shabo people, ethnonym, Shabo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shabo Context triple: [Shabo people, ethnonym, Shabo]
-
A.
Shabo
chosen
Shabo is a nearly extinct and poorly documented language isolate spoken by a small community in southwestern Ethiopia.
-
B.
Shabako
Shabako is an alternative name for Shabaka, a Kushite pharaoh of Egypt’s Twenty-fifth Dynasty known for consolidating Nubian rule over Egypt.
-
C.
Shabara
Shabara was an early Indian philosopher and commentator best known for his influential exegesis on the Purva Mimamsa school of Hindu philosophy.
-
D.
Shiban
Shiban was a Mongol prince of the Golden Horde, a son of Jochi and grandson of Genghis Khan who founded the Shibanid line.
-
E.
Shambuko
Shambuko is a town and administrative center located in the Gash-Barka region of western Eritrea.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f2138081909408c7916cef99c9 |
completed | April 9, 2026, 10:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5e911c03c819081f1447b320dd2f2 |
completed | April 20, 2026, 8:51 a.m. |
Created at: April 8, 2026, 9:35 p.m.