Triple
T26953725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oktoechos hymn book |
E678840
|
entity |
| Predicate | daySpecialization |
P161371
|
FINISHED |
| Object | Sunday resurrectional cycle |
—
|
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: Sunday resurrectional cycle | Statement: [Oktoechos hymn book, daySpecialization, Sunday resurrectional cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: daySpecialization Context triple: [Oktoechos hymn book, daySpecialization, Sunday resurrectional cycle]
-
A.
subjectSpecialization
Indicates that one subject focuses on, or has expertise in, a particular field, topic, or area of knowledge.
-
B.
dayType
Indicates the classification or category of a given day based on its characteristics or role (e.g., weekday, weekend, holiday).
-
C.
uniformSpecialty
Indicates that multiple entities share the same specific specialty, expertise, or area of focus.
-
D.
isHolidaySpecialOf
Indicates that something is a special version, event, or offering specifically created for or associated with a particular holiday.
-
E.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
- 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f620e5a0608190839a7ca4d6f89ec0 |
completed | May 2, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 27, 2026, 6:26 a.m.