Triple
T547418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Blair |
E12762
|
entity |
| Predicate | language |
P15
|
FINISHED |
| Object | Bengali |
E5055
|
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: Bengali | Statement: [Port Blair, language, Bengali]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bengali Context triple: [Port Blair, language, Bengali]
-
A.
Bengali
chosen
Bengali is an Indo-Aryan language spoken primarily in the Bengal region of South Asia and serving as the official and most widely used language of Bangladesh and the Indian state of West Bengal.
-
B.
Bangladeshi
Bangladeshi refers to a person or attribute associated with Bangladesh, particularly its people, nationality, or cultural heritage.
-
C.
Bhojpuri
Bhojpuri is an Indo-Aryan language spoken primarily in eastern Uttar Pradesh, western Bihar, and parts of Nepal, with a rich folk culture and a large diaspora community.
-
D.
Hindi
Hindi is an Indo-Aryan language widely spoken across northern and central India and used in government, education, media, and popular culture.
-
E.
Bengali script
Bengali script is an abugida used across eastern South Asia to write languages such as Bengali and Assamese, derived from the ancient Brahmi script.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a498e2e8c88190a66d759ed3094e18 |
completed | March 1, 2026, 7:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a4e02e0c1c81908fcb5356dc2b8f97 |
completed | March 2, 2026, 12:56 a.m. |
Created at: March 1, 2026, 7:32 p.m.