Triple
T6576869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaxabu language |
E157187
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | Bunun language |
E138017
|
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: Bunun language | Statement: [Kaxabu language, relatedTo, Bunun language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bunun language Context triple: [Kaxabu language, relatedTo, Bunun language]
-
A.
Bunun language
chosen
The Bunun language is an Austronesian language spoken by the Bunun indigenous people of central and southern Taiwan, known for its complex verb morphology and rich oral traditions.
-
B.
Bo language
Bo language is an extinct Great Andamanese language once spoken by the Bo people of the Andaman Islands in India.
-
C.
Budong-Budong language
The Budong-Budong language is an Austronesian language spoken by a small community in West Sulawesi, Indonesia.
-
D.
Boro language
Boro language is a Tibeto-Burman language spoken primarily by the Boro people of Assam in northeastern India.
-
E.
Buga language
The Buga language is a lesser-known member of the Khoe family of southern African languages, spoken by a small community and considered endangered.
- 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_69c6882b3a108190b3a9eb343ae4162c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ae7399488190b5f6948c60188aec |
completed | March 27, 2026, 4:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6cba0182c8190a30bc5e6fea4680e |
completed | March 27, 2026, 6:25 p.m. |
Created at: March 27, 2026, 1:54 p.m.