Triple
T7365166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golaghat district |
E169851
|
entity |
| Predicate | majorTown |
P316
|
FINISHED |
| Object | Bokakhat |
E168033
|
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: Bokakhat | Statement: [Golaghat district, majorTown, Bokakhat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bokakhat Context triple: [Golaghat district, majorTown, Bokakhat]
-
A.
Bokakhat
chosen
Bokakhat is a small town in Assam, India, known primarily as a gateway and service hub for visitors to Kaziranga National Park.
-
B.
Khaltahi
Khaltahi is a regional dialect of the Chhattisgarhi language spoken in parts of central India.
-
C.
Bawku
Bawku is a town in northeastern Ghana known as a commercial hub near the country’s border with Burkina Faso.
-
D.
Bhailsa
Bhailsa is the former historical name of Vidisha, an ancient city in the central Indian state of Madhya Pradesh known for its rich archaeological and cultural heritage.
-
E.
Bishutan
Bishutan is a character in the Persian epic Shahnameh, known as the loyal brother of the hero Esfandiyar.
- 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_69c68a5ade988190885b7175f63b7534 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f161d76081909da6d698fb3d8bb1 |
completed | March 27, 2026, 9:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7fab704008190ad07e12ead1a13ed |
completed | March 28, 2026, 3:58 p.m. |
Created at: March 27, 2026, 3:06 p.m.