Triple

T33674683
Position Surface form Disambiguated ID Type / Status
Subject Corsignano E862725 entity
Predicate laterUrbanForm P37688 FINISHED
Object ideal Renaissance city of Pienza 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: ideal Renaissance city of Pienza | Statement: [Corsignano, laterUrbanForm, ideal Renaissance city of Pienza]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: laterUrbanForm
Context triple: [Corsignano, laterUrbanForm, ideal Renaissance city of Pienza]
  • A. urbanMorphology chosen
    Indicates the spatial form, structure, and layout relationships that characterize the physical configuration of an urban area.
  • B. isUrbanForm
    Indicates that an entity represents or exhibits characteristics of an urban built environment or city-like spatial structure.
  • C. urbanDesign
    Indicates the relationship in which an entity is responsible for planning, organizing, or shaping the physical layout and functional structure of urban spaces.
  • D. containsUrbanForm
    Indicates that one entity spatially includes or encompasses an urban form or built-up area within its extent.
  • E. urbanScale
    Indicates the extent or magnitude of development, density, or size at which an area or environment can be characterized as urban.
  • 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_69f34985885c8190914322f492e04703 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fffc783b648190bcd7df017514d206 completed May 10, 2026, 3:33 a.m.
PD Predicate disambiguation batch_69fffc03fa24819099e12413dc6e0afd completed May 10, 2026, 3:31 a.m.
Created at: May 1, 2026, 1:43 a.m.