Triple
T16364999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurage people |
E397411
|
entity |
| Predicate | nativeLanguage |
P151
|
FINISHED |
| Object | Gumer language |
E397415
|
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: Gumer language | Statement: [Gurage people, nativeLanguage, Gumer language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gumer language Context triple: [Gurage people, nativeLanguage, Gumer language]
-
A.
Gumer language
chosen
The Gumer language is an Afroasiatic Semitic language spoken by the Gumer people of the Gurage region in central Ethiopia.
-
B.
Chumburung language
The Chumburung language is a Niger-Congo language spoken primarily by the Chumburung people in Ghana.
-
C.
Gurene language
The Gurene language is a Gur language spoken primarily by the Frafra people in northern Ghana and parts of Burkina Faso.
-
D.
Rumsen language
Rumsen language is an extinct Ohlone (Costanoan) Native American language formerly spoken in the Monterey Bay area of California.
-
E.
Godoberi language
The Godoberi language is a Northeast Caucasian (Nakh-Daghestanian) language spoken by the Godoberi people in the Republic of Dagestan, Russia.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2ff3bb5e481909669164a37d76b19 |
completed | April 18, 2026, 3:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a002dc0b3d4819089e6fba536ec8a11 |
completed | May 10, 2026, 7:03 a.m. |
Created at: April 10, 2026, 5:08 a.m.