Triple

T185272
Position Surface form Disambiguated ID Type / Status
Subject Baroque E3965 entity
Predicate hasArchitecturalFeature P6684 FINISHED
Object curved forms 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: curved forms | Statement: [Baroque, hasArchitecturalFeature, curved forms]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasArchitecturalFeature
Context triple: [Baroque, hasArchitecturalFeature, curved forms]
  • A. architecturalStyle
    Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
  • B. architectureType
    Indicates the specific style or category of architecture that characterizes or defines an entity.
  • C. hasUrbanFeature
    Indicates that a place or area possesses a specific urban element or infrastructure feature (such as roads, parks, or buildings) as part of its built environment.
  • D. hasCulturalFeature
    Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
  • E. significantBuilding
    Indicates that a building holds notable importance, prominence, or special status within a particular context (e.g., historical, cultural, architectural, or functional).
  • F. None of above. chosen

Provenance (4 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_69a25497e2f08190a040f8c6e1842643 completed Feb. 28, 2026, 2:36 a.m.
NER Named-entity recognition batch_69a2592867108190b5d316c055575449 completed Feb. 28, 2026, 2:55 a.m.
PD Predicate disambiguation batch_69a2566fb08c81908faff2fde552105d completed Feb. 28, 2026, 2:43 a.m.
PDg Predicate description generation batch_69a257e763d081908c54ad57d8d3060d completed Feb. 28, 2026, 2:50 a.m.
Created at: Feb. 28, 2026, 2:40 a.m.