Triple
T13367762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aka-Bo |
E318983
|
entity |
| Predicate | languageShiftTo |
P4292
|
FINISHED |
| Object | Andamanese Hindi |
E81134
|
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: Andamanese Hindi | Statement: [Aka-Bo, languageShiftTo, Andamanese Hindi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Andamanese Hindi Context triple: [Aka-Bo, languageShiftTo, Andamanese Hindi]
-
A.
Andaman Hindi
chosen
Andaman Hindi is a regional variety of Hindi that serves as a lingua franca among diverse communities in the Andaman Islands, including Great Andamanese speakers.
-
B.
Andamanese
Andamanese refers to the indigenous peoples and their distinct language families native to the Andaman Islands in the Bay of Bengal.
-
C.
Nagpuri
Nagpuri is an Indo-Aryan language spoken primarily in parts of eastern India, especially in and around the present-day state of Jharkhand.
-
D.
Bagheli
Bagheli is an Indo-Aryan language spoken primarily in the Bagelkhand region of central India, closely related to Hindi and used by millions as a regional vernacular.
-
E.
Mayurkhandi
Mayurkhandi is an early historic town in India that once served as a former capital of the Rashtrakuta dynasty.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadcd652d48190a782fd1f57f34b6a |
completed | April 11, 2026, 11:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f72680df088190b8dbcc8ad0d7366e |
completed | May 3, 2026, 10:42 a.m. |
Created at: April 9, 2026, 9:32 p.m.