Triple

T30986585
Position Surface form Disambiguated ID Type / Status
Subject Church of the Apostles E789542 entity
Predicate hasArchitecturePurpose P40127 FINISHED
Object 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: Christian liturgy | Statement: [Church of the Apostles, hasArchitecturePurpose, Christian liturgy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasArchitecturePurpose
Context triple: [Church of the Apostles, hasArchitecturePurpose, Christian liturgy]
  • A. usesArchitecture
    Indicates that one entity is built, implemented, or operates according to the architectural style, framework, or design specified by another entity.
  • B. hasArchitectureBy
    Indicates that an entity’s architectural design was created or authored by a specified architect or architectural firm.
  • C. usesArchitectureComponent
    Indicates that one entity employs or incorporates a specific architecture component as part of its structure, design, or implementation.
  • D. architecturalUse
    Indicates how a structure, space, or element is intended to be used or function within an architectural context.
  • E. purposeOfConstruction chosen
    Indicates that one entity was constructed or built in order to serve, enable, or fulfill the function, goal, or intended use represented by 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_69f224c550b081909ddfceb0c3d03bdd completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fd09840ea88190a2e6d7e577ade717 completed May 7, 2026, 9:52 p.m.
PD Predicate disambiguation batch_69fd064c49988190afadddbd04d7cb94 completed May 7, 2026, 9:38 p.m.
Created at: April 29, 2026, 8:56 p.m.