Triple
T19660000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shahdara district |
E472054
|
entity |
| Predicate | hasNeighbourhood |
P4813
|
FINISHED |
| Object | Seelampur |
—
|
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: Seelampur | Statement: [Shahdara district, hasNeighbourhood, Seelampur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Seelampur Context triple: [Shahdara district, hasNeighbourhood, Seelampur]
-
A.
Seelampur
chosen
Seelampur is a densely populated residential and commercial locality in East Delhi, India, known for its bustling markets and proximity to Shahdara.
-
B.
Kalyanpur
Kalyanpur is a town located in the Devbhoomi Dwarka district of the western Indian state of Gujarat.
-
C.
Bhaderwahi
Bhaderwahi is an Indo-Aryan language spoken primarily in the Bhaderwah region of Jammu and Kashmir, India.
-
D.
Alipur
Alipur is a city in southern Punjab, Pakistan, known as a local commercial and administrative center in the Muzaffargarh District.
-
E.
Alipur
Alipur is a locality in the northern part of Delhi, India, known for its role in regional governance and its mix of urban and semi-rural character.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6414993ac8190b6da3702b1924b24 |
completed | April 20, 2026, 3:07 p.m. |
Created at: April 10, 2026, 1:45 p.m.