Triple

T23935457
Position Surface form Disambiguated ID Type / Status
Subject Susques E602622 entity
Predicate religiousBuildingStyle P69416 FINISHED
Object colonial adobe 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: colonial adobe church | Statement: [Susques, religiousBuildingStyle, colonial adobe church]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: religiousBuildingStyle
Context triple: [Susques, religiousBuildingStyle, colonial adobe church]
  • A. hasReligiousBuildingStyle chosen
    Indicates that one entity (typically a building) exhibits or is characterized by the architectural style associated with a particular religion or religious tradition.
  • B. religiousBuildingInstanceOf
    Indicates that a specific religious building is an instance of a particular class or type of religious building.
  • C. inReligiousStructure
    Indicates that one entity is located within or inside a building or structure used for religious purposes.
  • D. religiousBuildingSpecialty
    Indicates that a religious building is specifically dedicated to or specializes in a particular religious function, practice, or tradition.
  • E. religiousBuildingDesigned
    Indicates that one entity (typically an architect or designer) is responsible for designing a religious building associated with the other entity.
  • 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_69e2953cf6e081909b8e25a10a52dddc completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f1cf9e8abc8190a3028a358265912e completed April 29, 2026, 9:30 a.m.
PD Predicate disambiguation batch_69f1615518088190a206f54e2fdb14a3 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 9:02 p.m.