Triple
T17274461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheila Dikshit |
E419350
|
entity |
| Predicate | placeOfBirth |
P1
|
FINISHED |
| Object | Kapurtala |
E1048124
|
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: Kapurtala | Statement: [Sheila Dikshit, placeOfBirth, Kapurtala]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kapurtala Context triple: [Sheila Dikshit, placeOfBirth, Kapurtala]
-
A.
Khandela
Khandela is a prominent town in Rajasthan, India, known historically as a local trading and cultural center in the Sikar region.
-
B.
Kotkapura
chosen
Kotkapura is a historic town and commercial center in the Faridkot district of Punjab, India, known for its textile and agricultural markets.
-
C.
Palsana
Palsana is a suburban area within the Surat metropolitan region in the Indian state of Gujarat, known for its growing residential and industrial development.
-
D.
Bhatapara
Bhatapara is a town and municipal council in the Baloda Bazar-Bhatapara district of Chhattisgarh, India, known primarily as a regional commercial and railway hub.
-
E.
Bhatapara
Bhatapara is a regional dialect of the Chhattisgarhi language spoken in and around the town of Bhatapara in the Indian state of Chhattisgarh.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e4332566c08190b4495dbbfe310ab6 |
completed | April 19, 2026, 1:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01794f6cf481909d76e3d61f9888c5 |
completed | May 11, 2026, 6:38 a.m. |
Created at: April 10, 2026, 5:40 a.m.