Triple
T20781738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tundla Junction |
E511497
|
entity |
| Predicate | servesCity |
P82
|
FINISHED |
| Object | Tundla |
E489133
|
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: Tundla | Statement: [Tundla Junction, servesCity, Tundla]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tundla Context triple: [Tundla Junction, servesCity, Tundla]
-
A.
Tundla
chosen
Tundla is a town in the Indian state of Uttar Pradesh known primarily as a major railway junction and transit hub in the Braj cultural region.
-
B.
Tindwari
Tindwari is a town and administrative settlement located in the Banda district of Uttar Pradesh, India.
-
C.
Takshaka
Takshaka is a prominent serpent king (naga) in Hindu mythology, best known for killing King Parikshit and thereby becoming the central target of King Janamejaya’s great snake sacrifice.
-
D.
Chetla
Chetla is a residential neighborhood in south Kolkata, India, known for its local markets, temples, and proximity to the Alipore area.
-
E.
Bhabra
Bhabra is a town in the Alirajpur district of Madhya Pradesh, India, known as the birthplace of Indian revolutionary Chandra Shekhar Azad.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c287b5288190823766fe59402d48 |
completed | April 21, 2026, 12:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a09006778fc8190a8e4fec8c1de7dc2 |
completed | May 16, 2026, 11:40 p.m. |
Created at: April 16, 2026, 12:38 p.m.