Triple

T30423010
Position Surface form Disambiguated ID Type / Status
Subject Georgian culture E773947 entity
Predicate architectureTradition P117362 FINISHED
Object Georgian ecclesiastical architecture 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: Georgian ecclesiastical architecture | Statement: [Georgian culture, architectureTradition, Georgian ecclesiastical architecture]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: architectureTradition
Context triple: [Georgian culture, architectureTradition, Georgian ecclesiastical architecture]
  • A. usesDesignTradition
    Indicates that one entity creates, interprets, or operates according to the established design principles, styles, or conventions associated with another entity or tradition.
  • B. buildingMaterialTradition
    Indicates the customary or historically established use of particular materials in the construction of a building or structure.
  • C. inArchitecturalCanon chosen
    Indicates that something is recognized as part of the established and authoritative body of works or principles in architecture.
  • D. builderTradition
    Indicates a relationship where an entity follows, embodies, or is associated with a particular tradition or customary practices of builders or construction craftsmanship.
  • E. traditionallyHouses
    Indicates that one entity has historically or customarily served as the location or container for another 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_69f22491ba248190b9a4776ca8e42d02 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f74c70fd248190a9d5543afcb08211 completed May 3, 2026, 1:24 p.m.
PD Predicate disambiguation batch_69f7478e3b548190a51d5d436e2bb036 completed May 3, 2026, 1:03 p.m.
Created at: April 29, 2026, 8:06 p.m.