Triple
T2019879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coptic Christmas |
E44079
|
entity |
| Predicate | usesCalendarBasis |
P5453
|
FINISHED |
| Object | Julian calendar-based liturgical tradition |
—
|
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-based liturgical tradition | Statement: [Coptic Christmas, usesCalendarBasis, Julian calendar-based liturgical tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCalendarBasis Context triple: [Coptic Christmas, usesCalendarBasis, Julian calendar-based liturgical tradition]
-
A.
usesCalendar
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
B.
calculationBasis
Indicates the rule, method, or reference standard used as the foundation for performing a calculation in the relationship.
-
C.
hasCalendarCustom
Indicates that an entity is associated with a customized or non-default calendar configuration or behavior.
-
D.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
E.
calendarType
chosen
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8d0bcbc8190bbbb726ecae1c51b |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.