Triple
T14629713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sultanpur |
E343445
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Ayodhya |
E26191
|
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: Ayodhya | Statement: [Sultanpur, locatedNear, Ayodhya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ayodhya Context triple: [Sultanpur, locatedNear, Ayodhya]
-
A.
Ayodhya
chosen
Ayodhya is an ancient city in India revered in Hinduism as the birthplace of Lord Rama and a major pilgrimage site.
-
B.
Mathura
Mathura is an ancient city in northern India revered in Hinduism as the birthplace of Lord Krishna and a major pilgrimage center.
-
C.
Agra
Agra is a historic city in northern India renowned for its Mughal-era architecture, most notably the Taj Mahal and Agra Fort.
-
D.
Indraprastha
Indraprastha is the legendary capital city of the Pandavas in the Indian epic Mahabharata, often identified with the region of present-day Delhi.
-
E.
Varanasi
Varanasi is an ancient city on the banks of the Ganges in northern India, revered as one of Hinduism’s holiest pilgrimage sites and a major center of religious, cultural, and spiritual life.
- 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4a7c8fc81909d10c1f563d7d1e7 |
completed | April 14, 2026, 9:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fde16e85488190b0dcc2ccd2f5df4d |
completed | May 8, 2026, 1:13 p.m. |
Created at: April 10, 2026, 1:26 a.m.