Triple

T32282899
Position Surface form Disambiguated ID Type / Status
Subject Qurbono E824747 entity
Predicate hasParallelConcept P57196 FINISHED
Object Divine Liturgy in Byzantine Rite NE NERFINISHED

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: Divine Liturgy in Byzantine Rite | Statement: [Qurbono, hasParallelConcept, Divine Liturgy in Byzantine Rite]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasParallelConcept
Context triple: [Qurbono, hasParallelConcept, Divine Liturgy in Byzantine Rite]
  • A. hasConceptualParallel chosen
    Indicates that one entity corresponds to or mirrors another at a conceptual level, showing a similar idea, structure, or pattern despite possible differences in form or context.
  • B. hasParallelIn
    Indicates that one entity has a corresponding or analogous counterpart in another context, system, or domain.
  • C. hasParallelTransit
    Indicates that one transit route, service, or segment runs in parallel to another along a similar path or corridor.
  • D. hasConcept
    Indicates that an entity includes, embodies, or is associated with a particular concept.
  • E. includesSpecialParallel
    Indicates that one entity contains or incorporates another entity in a way that involves a designated special type of parallel relationship or structure between them.
  • 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_69f3490f404081908450db66884f4334 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fef8c3f2388190b995ec173512945a completed May 9, 2026, 9:05 a.m.
PD Predicate disambiguation batch_69fef65975608190960b78d27e806d4f completed May 9, 2026, 8:54 a.m.
Created at: May 1, 2026, 12:43 a.m.