Triple
T7515169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agnigarh |
E177620
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Tezpur |
E33380
|
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: Tezpur | Statement: [Agnigarh, location, Tezpur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tezpur Context triple: [Agnigarh, location, Tezpur]
-
A.
Tezpur
chosen
Tezpur is a historic city in northeastern India known for its cultural heritage, archaeological sites, and scenic location on the banks of the Brahmaputra River.
-
B.
Tinsukia
Tinsukia is a town in Assam, India, known as a commercial hub of the region and a gateway to nearby wildlife-rich areas such as Dibru-Saikhowa National Park.
-
C.
Dibrugarh
Dibrugarh is a prominent city in northeastern India known as a major commercial and industrial hub of Assam, especially for its tea industry and oil and natural gas sectors.
-
D.
Jorhat
Jorhat is a prominent city in northeastern India known as a cultural and educational hub and a key center of the tea industry in Assam.
-
E.
Dimapur
Dimapur is a major commercial and transportation hub in northeastern India, serving as the primary gateway to the state of Nagaland.
- 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_69c69f2891148190a484f3b8222c6f1b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5f44dd48190b2b093aab9a196c8 |
completed | March 27, 2026, 9:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c9bcbe7f488190aee034a51e8a281b |
completed | March 29, 2026, 11:58 p.m. |
Created at: March 27, 2026, 3:45 p.m.