Triple
T6014507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shivpuri railway station |
E133914
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Shivpuri |
E133914
|
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: Shivpuri | Statement: [Shivpuri railway station, locatedIn, Shivpuri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shivpuri Context triple: [Shivpuri railway station, locatedIn, Shivpuri]
-
A.
Shivpuri
chosen
Shivpuri is a historic town and former princely state in central India, known for its forests, wildlife sanctuaries, and royal palaces.
-
B.
Sohagpur
Sohagpur is a town in the Narmadapuram district of Madhya Pradesh, India, known as a local commercial center and access point to nearby forested and wildlife areas.
-
C.
Tuljapur
Tuljapur is a town in Maharashtra, India, renowned as a major pilgrimage center for the goddess Bhavani.
-
D.
Bhind
Bhind is a city in the northern part of the Indian state of Madhya Pradesh, known as an administrative and commercial center of the region.
-
E.
Karauli
Karauli is a historic town and pilgrimage center in the Indian state of Rajasthan, known for its ancient temples and distinctive red sandstone architecture.
- 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_69c0087361a48190905c6b55969852b8 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f544fd88190b6777c4db04e274f |
completed | March 22, 2026, 8:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c5e3a5d54c8190b2bc8b3291f8ac2f |
completed | March 27, 2026, 1:55 a.m. |
Created at: March 22, 2026, 4:06 p.m.