Triple
T28240717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malviya Nagar |
E712016
|
entity |
| Predicate | hasNearbyCommercialHub |
P191961
|
FINISHED |
| Object | Saket District Centre |
—
|
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: Saket District Centre | Statement: [Malviya Nagar, hasNearbyCommercialHub, Saket District Centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyCommercialHub Context triple: [Malviya Nagar, hasNearbyCommercialHub, Saket District Centre]
-
A.
hasNearbyCommercialFacilities
chosen
Indicates that a place is located close to one or more commercial facilities, such as shops, restaurants, or other businesses.
-
B.
hasMajorCompanyNearby
Indicates that a location or entity is situated close to at least one large or significant company.
-
C.
hasOutletNear
Indicates that one entity has a physical outlet or branch located in close proximity to another specified location or entity.
-
D.
connectsToCommercialArea
Indicates that one location has a direct link, route, or access path to a commercial area.
-
E.
hasNearbyFacility
Indicates that one entity is located close to or in the vicinity of a particular facility.
- F. None of above.
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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: April 27, 2026, 10:58 p.m.