Triple
T9493172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arts Square ensemble |
E228938
|
entity |
| Predicate | cityPlanningType |
P22625
|
FINISHED |
| Object | regular layout |
—
|
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: regular layout | Statement: [Arts Square ensemble, cityPlanningType, regular layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityPlanningType Context triple: [Arts Square ensemble, cityPlanningType, regular layout]
-
A.
urbanPlanningFunction
Indicates a functional role or purpose that something serves within the planning, organization, or management of urban spaces and infrastructure.
-
B.
urbanDevelopmentType
Indicates the specific category or nature of urban development associated with or applied to an entity (e.g., residential, commercial, mixed-use).
-
C.
urbanDesignType
Indicates the specific category or style of urban design that characterizes or is applied to a place or project.
-
D.
urbanPlanningStyle
chosen
Indicates the characteristic approach or methodology used in planning and organizing urban spaces and development.
-
E.
urbanPlanInspiredBy
Indicates that an urban planning design, strategy, or project is conceptually derived from, modeled on, or significantly influenced by another plan, precedent, or source.
- 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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd95e8c8908190950e1130f9612823 |
completed | April 1, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:56 p.m.