Triple
T21815489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blanga |
E538595
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Blablanga |
—
|
NE NERFINISHED |
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: Blablanga | Statement: [Blanga, hasAlternativeName, Blablanga]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Blablanga Context triple: [Blanga, hasAlternativeName, Blablanga]
-
A.
Blablanga
Blablanga is an Austronesian language spoken in the Solomon Islands, belonging to the Meso-Melanesian subgroup.
-
B.
Menongue
Menongue is a city in southeastern Angola that serves as the administrative and economic center of Cuando Cubango Province.
-
C.
Blanga
chosen
Blanga is an Austronesian language spoken primarily on the island of Santa Isabel in the Solomon Islands.
-
D.
Blang
The Blang are an ethnic minority group primarily living in the mountainous regions of Yunnan Province in China, known for their tea cultivation and distinct language and culture.
-
E.
Mbalanhu
Mbalanhu is a Bantu language variety spoken by a subgroup of the Ovambo people in northern Namibia and southern Angola.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07cc99bbc8190bf074930f361af7d |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 16, 2026, 6:54 p.m.