Triple
T11335580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaipur district |
E268462
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Shahpura |
E798787
|
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: Shahpura | Statement: [Jaipur district, contains, Shahpura]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shahpura Context triple: [Jaipur district, contains, Shahpura]
-
A.
Shahpura
chosen
Shahpura is a town in Rajasthan, India, historically known as the administrative and cultural center of the former princely Shahpura State.
-
B.
Sikandarpur
Sikandarpur is a metro station in the Delhi Metro network that serves the Gurugram area and provides an interchange with the Rapid Metro system.
-
C.
Khalapur
Khalapur is a town and taluka in Maharashtra, India, known for its location along major highways and proximity to industrial and tourist hubs in the Raigad region.
-
D.
Hoshangabad
Hoshangabad is a city in the Indian state of Madhya Pradesh, known for its location on the banks of the Narmada River and its agricultural and industrial activities.
-
E.
Sadulshahar
Sadulshahar is a town in the northern Indian state of Rajasthan, situated within the Ganganagar district near the border with Punjab.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9ff62c88190a089dd84e2ac1d17 |
completed | April 9, 2026, 6:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e55645d8bc8190b338c05ee382d5fc |
completed | April 19, 2026, 10:25 p.m. |
Created at: April 8, 2026, 9:33 p.m.