Triple
T25120917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Сыропустная неделя |
E629262
|
entity |
| Predicate | isInCalendar |
P96907
|
FINISHED |
| Object | Eastern Orthodox liturgical calendar |
—
|
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: Eastern Orthodox liturgical calendar | Statement: [Сыропустная неделя, isInCalendar, Eastern Orthodox liturgical calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInCalendar Context triple: [Сыропустная неделя, isInCalendar, Eastern Orthodox liturgical calendar]
-
A.
usesCalendar
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
B.
usesCalendarEvent
Indicates that one entity makes use of, interacts with, or relies on a specific calendar event.
-
C.
hasFunctionInCalendar
chosen
Indicates that something serves a specific role or performs a particular function within a calendar system or scheduling context.
-
D.
isFollowedInCalendarBy
Indicates that one event or time period occurs immediately after another in a calendar sequence.
-
E.
includedCalendarApp
Indicates that a calendar application is bundled or provided as part of a larger product, service, or system.
- 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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f465cbc8e08190b7c35e36a94ea703 |
completed | May 1, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:28 a.m.