Triple
T6187821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dholera |
E138105
|
entity |
| Predicate | smartCityFeaturesPlanned |
P50320
|
FINISHED |
| Object | integrated ICT infrastructure |
—
|
LITERAL 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: integrated ICT infrastructure | Statement: [Dholera, smartCityFeaturesPlanned, integrated ICT infrastructure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: smartCityFeaturesPlanned Context triple: [Dholera, smartCityFeaturesPlanned, integrated ICT infrastructure]
-
A.
smartCityProjects
chosen
Indicates a relationship where a city undertakes or is associated with projects that apply digital, data-driven, or intelligent technologies to improve urban services and infrastructure.
-
B.
plannedDevelopment
Indicates that one entity has been designated or scheduled for future development or construction by another entity.
-
C.
urbanPlanningFunction
Indicates a functional role or purpose that something serves within the planning, organization, or management of urban spaces and infrastructure.
-
D.
mainUrbanPlan
Indicates the primary urban planning scheme or framework that governs the development and organization of a given area.
-
E.
isPlannedCity
Indicates that a city has been deliberately designed and constructed according to a pre-established urban plan rather than developing organically over time.
- 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_69c008a8fd408190b7ec6e42934974a6 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06217be288190997032c8c4839fa5 |
completed | March 22, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:19 p.m.