Triple

T20049
Position Surface form Disambiguated ID Type / Status
Subject Eastern Orthodox Christianity E398 entity
Predicate usesCalendar P1818 FINISHED
Object Julian calendar in many churches 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: Julian calendar in many churches | Statement: [Eastern Orthodox Christianity, usesCalendar, Julian calendar in many churches]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesCalendar
Context triple: [Eastern Orthodox Christianity, usesCalendar, Julian calendar in many churches]
  • A. academicCalendar
    Indicates the schedule or structure of academic terms, sessions, and key dates associated with an educational institution or program.
  • B. hasImportantHoliday
    Indicates that an entity is associated with a holiday considered significant or special in some context.
  • C. meetsAs
    Indicates that two entities encounter or come together at the same place and time, typically in a planned or recognized interaction.
  • D. meets
    Indicates that two or more entities come together at the same place and time, typically for interaction or a shared purpose.
  • E. nationalHoliday
    Indicates that a particular day is officially recognized and observed as a national holiday by a country or nation.
  • F. None of above. chosen

Provenance (4 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_69a240778d288190815c0052ebbbcc91 completed Feb. 28, 2026, 1:10 a.m.
NER Named-entity recognition batch_69a24703cb988190ad2bc181d27829e4 completed Feb. 28, 2026, 1:38 a.m.
PD Predicate disambiguation batch_69a24650f1f0819081e638fafd18d687 completed Feb. 28, 2026, 1:35 a.m.
PDg Predicate description generation batch_69a24702d4988190a54a4e578b7c919e completed Feb. 28, 2026, 1:38 a.m.
Created at: Feb. 28, 2026, 1:14 a.m.