Triple
T10489833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surmic languages |
E247385
|
entity |
| Predicate | includesLanguage |
P2177
|
FINISHED |
| Object |
Baale language
Baale language is a Surmic language spoken by the Baale (Suri) people of southwestern Ethiopia and neighboring regions.
|
E867489
|
NE FINISHED |
How this triple was built (4 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: Baale language | Statement: [Surmic languages, includesLanguage, Baale language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Baale language Context triple: [Surmic languages, includesLanguage, Baale language]
-
A.
Balantak language
The Balantak language is an Austronesian language spoken by the Balantak people of eastern Central Sulawesi, Indonesia.
-
B.
Baule language
The Baule language is a Central Tano language of the Akan group spoken primarily by the Baoulé people in Côte d'Ivoire.
-
C.
Baliledu language
The Baliledu language is an Austronesian language of the Bima–Sumba subgroup spoken by a local community in eastern Indonesia.
-
D.
Batuley language
The Batuley language is an Austronesian language spoken by a small community in Indonesia’s Aru Islands.
-
E.
Belhare language
The Belhare language is a Kiranti language of the Sino-Tibetan family spoken by the Belhare community in eastern Nepal.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Baale language Triple: [Surmic languages, includesLanguage, Baale language]
Generated description
Baale language is a Surmic language spoken by the Baale (Suri) people of southwestern Ethiopia and neighboring regions.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Baale language Target entity description: Baale language is a Surmic language spoken by the Baale (Suri) people of southwestern Ethiopia and neighboring regions.
-
A.
Balantak language
The Balantak language is an Austronesian language spoken by the Balantak people of eastern Central Sulawesi, Indonesia.
-
B.
Baule language
The Baule language is a Central Tano language of the Akan group spoken primarily by the Baoulé people in Côte d'Ivoire.
-
C.
Baliledu language
The Baliledu language is an Austronesian language of the Bima–Sumba subgroup spoken by a local community in eastern Indonesia.
-
D.
Batuley language
The Batuley language is an Austronesian language spoken by a small community in Indonesia’s Aru Islands.
-
E.
Belhare language
The Belhare language is a Kiranti language of the Sino-Tibetan family spoken by the Belhare community in eastern Nepal.
- F. None of above. chosen
Provenance (5 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_69d5097ca5c081908b47a08ca7885650 |
completed | April 7, 2026, 1:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d8dc9792308190b09d6aaed63dd418 |
completed | April 10, 2026, 11:18 a.m. |
| NEDg | Description generation | batch_69d8e8c81bdc8190b6b6dfe00025b514 |
completed | April 10, 2026, 12:10 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d901ef24608190934377d9dc855d6f |
completed | April 10, 2026, 1:58 p.m. |
Created at: April 6, 2026, 12:23 p.m.