Triple

T9711052
Position Surface form Disambiguated ID Type / Status
Subject Kuortane E235022 entity
Predicate churchArchitecturalStyle P607 FINISHED
Object wooden church 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: wooden church | Statement: [Kuortane, churchArchitecturalStyle, wooden church]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: churchArchitecturalStyle
Context triple: [Kuortane, churchArchitecturalStyle, wooden church]
  • A. parishChurchArchitectureStyle
    Indicates the architectural style or design tradition in which a parish church is built or characterized.
  • B. ecclesiasticalStyle
    Indicates the formal religious or clerical style or title by which an ecclesiastical person is properly addressed.
  • C. hasReligiousBuildingStyle
    Indicates that one entity (typically a building) exhibits or is characterized by the architectural style associated with a particular religion or religious tradition.
  • D. architecturalStyle chosen
    Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
  • E. hasCathedralStyle
    Indicates that something possesses or is characterized by a particular architectural style associated with a cathedral.
  • 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_69ca84cd8fa0819090a5e243ceb37003 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9e0591208190aa57cc9e2aebafb7 completed April 1, 2026, 10:36 p.m.
PD Predicate disambiguation batch_69cd03bfeca08190924fca43aaa9c10f completed April 1, 2026, 11:38 a.m.
Created at: March 30, 2026, 8:19 p.m.