Triple
T24351091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quadratestadt |
E613790
|
entity |
| Predicate | denotesUrbanForm |
P37688
|
FINISHED |
| Object | orthogonal street grid |
—
|
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: orthogonal street grid | Statement: [Quadratestadt, denotesUrbanForm, orthogonal street grid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesUrbanForm Context triple: [Quadratestadt, denotesUrbanForm, orthogonal street grid]
-
A.
containsUrbanForm
Indicates that one entity spatially includes or encompasses an urban form or built-up area within its extent.
-
B.
isUrbanForm
Indicates that an entity represents or exhibits characteristics of an urban built environment or city-like spatial structure.
-
C.
formsUrbanAreaWith
Indicates that two or more settlements are geographically and functionally connected so that together they constitute a single continuous urban area.
-
D.
urbanDesignType
Indicates the specific category or style of urban design that characterizes or is applied to a place or project.
-
E.
urbanMorphology
chosen
Indicates the spatial form, structure, and layout relationships that characterize the physical configuration of an urban area.
- 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293457120819098af138fdd01846d |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:59 a.m.