Triple
T11007687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ELCH |
E260162
|
entity |
| Predicate | observesChurchYear |
P9168
|
FINISHED |
| Object | liturgical calendar |
—
|
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: liturgical calendar | Statement: [ELCH, observesChurchYear, liturgical calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observesChurchYear Context triple: [ELCH, observesChurchYear, liturgical calendar]
-
A.
usesLiturgicalCalendar
chosen
Indicates that an entity follows or organizes its religious observances according to a formal liturgical calendar.
-
B.
dateInEasternOrthodoxChurches
Indicates that the specified date is observed or used according to the liturgical calendar of Eastern Orthodox churches.
-
C.
observanceMayVaryByYear
Indicates that the way an observance is recognized, scheduled, or practiced can differ from one year to another.
-
D.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
E.
isEasternCatholic
Indicates that one entity belongs to, practices, or is affiliated with an Eastern Catholic Church in relation to another entity or classification.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79757bdcc8190900b267826eece21 |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.