Triple
T29434252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dankaur |
E746522
|
entity |
| Predicate | hasNearbyUrbanProject |
P79682
|
FINISHED |
| Object | Yamuna Expressway Industrial Development Authority area |
—
|
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: Yamuna Expressway Industrial Development Authority area | Statement: [Dankaur, hasNearbyUrbanProject, Yamuna Expressway Industrial Development Authority area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyUrbanProject Context triple: [Dankaur, hasNearbyUrbanProject, Yamuna Expressway Industrial Development Authority area]
-
A.
hasNearbyProject
Indicates that one entity has a project located within a close or specified proximity to another entity or reference point.
-
B.
isPartOfUrbanProject
Indicates that something belongs to, is included within, or constitutes a component of a broader urban development project.
-
C.
hasNearbyDevelopment
chosen
Indicates that a development or construction project exists in close physical proximity to the referenced entity.
-
D.
hasUrbanProximity
Indicates that one entity is located near or within easy access to an urban area associated with another entity.
-
E.
nearbyProject
Indicates that one entity is located close to or in the immediate vicinity of another entity or project.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: April 28, 2026, 3:15 p.m.