Triple
T11851637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaipur Walled City |
E281921
|
entity |
| Predicate | urbanPlanningPrinciple |
P95143
|
FINISHED |
| Object | grid plan |
—
|
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: grid plan | Statement: [Jaipur Walled City, urbanPlanningPrinciple, grid plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanPlanningPrinciple Context triple: [Jaipur Walled City, urbanPlanningPrinciple, grid plan]
-
A.
urbanPlanningFunction
Indicates a functional role or purpose that something serves within the planning, organization, or management of urban spaces and infrastructure.
-
B.
urbanPlanningTheme
Indicates a thematic relationship in which an entity is concerned with, addresses, or is categorized under topics related to urban planning.
-
C.
urbanPlanningOutcome
Indicates the result or impact that urban planning decisions or processes have on a place, system, or population.
-
D.
urbanPlanningForm
chosen
Indicates the specific type or structure of urban planning approach applied to a place or development.
-
E.
urbanPlanningStyle
Indicates the characteristic approach or methodology used in planning and organizing urban spaces and development.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a696ee548190800d56c64c339b10 |
completed | April 10, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.