Triple
T18836346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daśapura |
E460673
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Dasapura |
—
|
NE NERFINISHED |
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: Dasapura | Statement: [Daśapura, hasAlternativeName, Dasapura]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dasapura Context triple: [Daśapura, hasAlternativeName, Dasapura]
-
A.
Daśapura
chosen
Daśapura is the ancient name of the city now known as Mandsaur in the Indian state of Madhya Pradesh, historically noted for its role as a regional center in central India.
-
B.
Dantapura
Dantapura was an ancient city traditionally identified as the royal and administrative center of the Kalinga kingdom in eastern India.
-
C.
Bhagwanpura
Bhagwanpura is a town in the Khargone district of Madhya Pradesh, India, known primarily as a local administrative and market center for surrounding rural areas.
-
D.
Hadapsar
Hadapsar is a rapidly developing suburb in the eastern part of Pune, India, known for its IT parks, residential complexes, and industrial areas.
-
E.
Pavapuri
Pavapuri is a revered Jain pilgrimage site in Bihar, India, best known as the place where Mahavira, the 24th Tirthankara, attained nirvana.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99e86388190957acaaab401b5cb |
completed | April 20, 2026, 4:20 a.m. |
Created at: April 10, 2026, 11:56 a.m.