Triple
T36470941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarum Use |
E898537
|
entity |
| Predicate | followsCalendarType |
P5453
|
FINISHED |
| Object | liturgical year of the Roman Rite |
—
|
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 year of the Roman Rite | Statement: [Sarum Use, followsCalendarType, liturgical year of the Roman Rite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsCalendarType Context triple: [Sarum Use, followsCalendarType, liturgical year of the Roman Rite]
-
A.
followsCalendarOf
Indicates that one entity adopts and adheres to the scheduling, events, or time structure defined by another entity’s calendar.
-
B.
isFollowedInCalendarBy
Indicates that one event or time period occurs immediately after another in a calendar sequence.
-
C.
usesCalendar
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
D.
calendarType
chosen
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
-
E.
followsGregorianCalendar
Indicates that the entity uses or adheres to the Gregorian calendar system for dating and timekeeping.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
Created at: May 3, 2026, 4:10 p.m.