Triple
T25192219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet architecture |
E630900
|
entity |
| Predicate | typicalUrbanForm |
P37688
|
FINISHED |
| Object | microrayon |
—
|
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: microrayon | Statement: [Soviet architecture, typicalUrbanForm, microrayon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUrbanForm Context triple: [Soviet architecture, typicalUrbanForm, microrayon]
-
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.
urbanScale
Indicates the extent or magnitude of development, density, or size at which an area or environment can be characterized as urban.
-
D.
urbanMorphology
chosen
Indicates the spatial form, structure, and layout relationships that characterize the physical configuration of an urban area.
-
E.
urbanAreaType
Indicates the classification of an area based on its urban characteristics or development type (e.g., city, town, suburb, metropolitan region).
- 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 21, 2026, 12:45 p.m.