Triple
T9686483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raichur railway station |
E234420
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | Raichur city |
E37145
|
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: Raichur city | Statement: [Raichur railway station, serves, Raichur city]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Raichur city Context triple: [Raichur railway station, serves, Raichur city]
-
A.
Raichur
chosen
Raichur is a historic city in the Indian state of Karnataka, known for its ancient forts, archaeological significance, and strategic location between major river systems.
-
B.
Bijapur
Bijapur is a historic city in the Indian state of Karnataka, renowned for its rich Islamic architecture and monuments from the medieval Deccan period.
-
C.
Yadgir
Yadgir is a district in the Indian state of Karnataka, known for its agricultural economy and historical forts and temples.
-
D.
Karmala
Karmala is a town in Maharashtra, India, known as a local administrative and commercial center within Solapur district.
-
E.
Nagole
Nagole is a residential and commercial neighborhood in Hyderabad, India, served as a key terminus and transit hub on the Hyderabad Metro network.
- 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9cd2dab481908e0d3fed28de9d40 |
completed | April 1, 2026, 10:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2284e9d0c8190ab09ad1fd0a123e3 |
completed | April 5, 2026, 9:15 a.m. |
Created at: March 30, 2026, 8:17 p.m.