Triple

T1657382
Position Surface form Disambiguated ID Type / Status
Subject Byzantine Revival E35830 entity
Predicate hasDesignInfluence P16767 FINISHED
Object Orthodox Christian liturgy 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: Orthodox Christian liturgy | Statement: [Byzantine Revival, hasDesignInfluence, Orthodox Christian liturgy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDesignInfluence
Context triple: [Byzantine Revival, hasDesignInfluence, Orthodox Christian liturgy]
  • A. hasLandscapeDesignInfluence
    Indicates that one entity has influenced or shaped the landscape design style, principles, or features of another entity.
  • B. hasDesign
    Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
  • C. architecturalInfluence chosen
    Indicates that one architectural style, structure, or designer has had a formative impact on the design, style, or features of another.
  • D. placeOfInfluence
    Indicates the location or area where an entity exerts significant impact, authority, or cultural, social, or intellectual influence.
  • E. influencedWork
    Indicates that one work has had a significant impact on the creation, style, content, or development of another work.
  • 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_69a88606aa808190aa0b421b4271f220 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69aaf3359ce48190803b322db8ad6027 completed March 6, 2026, 3:31 p.m.
PD Predicate disambiguation batch_69a907cff53c8190b424f088478d3e2c completed March 5, 2026, 4:34 a.m.
Created at: March 4, 2026, 7:29 p.m.