Triple
T23621163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mass |
E583321
|
entity |
| Predicate | dayOfObligationFor |
P8511
|
FINISHED |
| Object | Sundays |
—
|
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: Sundays | Statement: [Mass, dayOfObligationFor, Sundays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dayOfObligationFor Context triple: [Mass, dayOfObligationFor, Sundays]
-
A.
designatedDayFor
Indicates that a specific day is officially assigned or reserved for a particular purpose, event, or activity.
-
B.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
C.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
D.
obligationCondition
chosen
Indicates that one situation or state serves as the condition under which an obligation for an entity becomes active or must be fulfilled.
-
E.
obligationType
Indicates the specific kind or category of duty, requirement, or commitment that applies within an obligation relationship.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b178d20c819094b547c6c7ae6c01 |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.