Triple
T16234888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South East Delhi district |
E394079
|
entity |
| Predicate | containsNeighborhood |
P4813
|
FINISHED |
| Object | Amar Colony |
E504665
|
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: Amar Colony | Statement: [South East Delhi district, containsNeighborhood, Amar Colony]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amar Colony Context triple: [South East Delhi district, containsNeighborhood, Amar Colony]
-
A.
Amar Colony
chosen
Amar Colony is a residential neighborhood in South Delhi, India, known for its dense housing, local markets, and proximity to major commercial areas.
-
B.
Dayanand Colony
Dayanand Colony is a residential neighborhood located within the Lajpat Nagar area of South Delhi, India.
-
C.
Pathan Colony
Pathan Colony is a residential neighborhood located within SITE Town in Karachi, Pakistan.
-
D.
Kailash Colony
Kailash Colony is an upscale residential and commercial neighborhood in South Delhi known for its central location, metro connectivity, and mix of markets, eateries, and housing.
-
E.
Bilal Colony
Bilal Colony is a residential neighborhood located within the Korangi District of Karachi, Pakistan.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24559af48819092e4b466778b07e2 |
completed | April 17, 2026, 2:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a000ed71f488190bcdc2dcc74e5c5d3 |
completed | May 10, 2026, 4:51 a.m. |
Created at: April 10, 2026, 5:04 a.m.