Triple
T8373676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Delhi |
E197519
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Alipur |
E738317
|
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: Alipur | Statement: [North Delhi, contains, Alipur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alipur Context triple: [North Delhi, contains, Alipur]
-
A.
Alipur
Alipur is a city in southern Punjab, Pakistan, known as a local commercial and administrative center in the Muzaffargarh District.
-
B.
Alipur
chosen
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.
-
C.
Ballabgarh
Ballabgarh is a historic town and industrial hub in the Faridabad district of Haryana, India, known for its markets, temples, and manufacturing activity.
-
D.
Bhaderwahi
Bhaderwahi is an Indo-Aryan language spoken primarily in the Bhaderwah region of Jammu and Kashmir, India.
-
E.
Azadpur
Azadpur is a locality in North Delhi, India, known for its major wholesale fruit and vegetable market and connectivity via the Delhi Metro.
- 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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80a7cab881909d8cca66a340dceb |
completed | March 31, 2026, 8:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cea813e384819090a8a7dc05e41ab2 |
completed | April 2, 2026, 5:32 p.m. |
Created at: March 30, 2026, 6:01 p.m.