Triple
T12554948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asur |
E295189
|
entity |
| Predicate | languageSpoken |
P151
|
FINISHED |
| Object | Asuri language |
E734619
|
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: Asuri language | Statement: [Asur, languageSpoken, Asuri language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Asuri language Context triple: [Asur, languageSpoken, Asuri language]
-
A.
Asuri language
chosen
Asuri language is an endangered Munda language of the Austroasiatic family spoken by the Asur tribal community in eastern India, primarily in Jharkhand.
-
B.
Anuki language
The Anuki language is an Oceanic language spoken by a small coastal community in Papua New Guinea’s Milne Bay Province.
-
C.
Arosi language
The Arosi language is an Oceanic language spoken primarily on Makira Island in the Solomon Islands.
-
D.
Ashkun language
The Ashkun language is a Nuristani language spoken by the Ashkun people in remote regions of eastern Afghanistan.
-
E.
Ansus language
The Ansus language is an Austronesian language spoken in eastern Indonesia, specifically in the South Halmahera–West New Guinea region.
- 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95490d2708190857f0cb9b8dd6a30 |
completed | April 10, 2026, 7:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65587524881908c933490bface976 |
completed | May 2, 2026, 7:50 p.m. |
Created at: April 8, 2026, 11:45 p.m.