Triple
T22458837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beary Muslims |
E555179
|
entity |
| Predicate | language |
P15
|
FINISHED |
| Object | Beary language |
—
|
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: Beary language | Statement: [Beary Muslims, language, Beary language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beary language Context triple: [Beary Muslims, language, Beary language]
-
A.
Beary language
chosen
Beary language is a Dravidian tongue spoken primarily by the Beary Muslim community in coastal Karnataka and parts of northern Kerala in India, characterized by influences from Tulu, Malayalam, and Arabic.
-
B.
Aka-Bea language
The Aka-Bea language is an extinct indigenous tongue once spoken by the Great Andamanese Aka-Bea people of the Andaman Islands in the Bay of Bengal.
-
C.
Bwekar language
The Bwekar language is a lesser-known Gbaya language spoken by a subgroup of the Gbaya people in Central Africa.
-
D.
Baelelea language
The Baelelea language is an Oceanic language spoken by the Baelelea people of Malaita in the Solomon 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.
- 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_69e11e51fdec8190adfdf9f8a6362221 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b7e01fc8190825c3dc024484440 |
completed | April 29, 2026, 1:14 a.m. |
Created at: April 16, 2026, 8:48 p.m.