Triple
T10483595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proto-Koman |
E247233
|
entity |
| Predicate | hasBranch |
P35
|
FINISHED |
| Object | Koman |
E247383
|
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: Koman | Statement: [Proto-Koman, hasBranch, Koman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Koman Context triple: [Proto-Koman, hasBranch, Koman]
-
A.
Koman
chosen
Koman is a small language family of northeastern Africa whose member languages are spoken primarily in border regions of Ethiopia and Sudan.
-
B.
Kambaata
Kambaata is a Cushitic language spoken primarily by the Kambaata people in southern Ethiopia.
-
C.
Kunama
Kunama is a Nilo-Saharan language spoken primarily by the Kunama people in western Eritrea and adjacent parts of Ethiopia.
-
D.
Haiman
Haiman is a surname and given name that serves as a variant form of "Hyman," often associated with individuals of Jewish heritage.
-
E.
Nabaloi
Nabaloi is an Austronesian language spoken by the Ibaloi people of the northern Philippines, particularly in the Benguet region of Luzon.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509678ac88190984f18a2162e2dcf |
completed | April 7, 2026, 1:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d8a03c647c81909521fee4a66ec8ac |
completed | April 10, 2026, 7:01 a.m. |
Created at: April 6, 2026, 12:22 p.m.