Triple
T6369009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midnight Office |
E143298
|
entity |
| Predicate | frequencyOfObservance |
P16914
|
FINISHED |
| Object | daily in monastic practice |
—
|
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: daily in monastic practice | Statement: [Midnight Office, frequencyOfObservance, daily in monastic practice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequencyOfObservance Context triple: [Midnight Office, frequencyOfObservance, daily in monastic practice]
-
A.
pilgrimageFrequency
Indicates how often an entity undertakes or participates in a pilgrimage.
-
B.
performedFrequency
chosen
Indicates how often an action or activity is carried out within a given time period.
-
C.
observance
Indicates the performance or maintenance of a practice, rule, or custom in accordance with prescribed or expected standards.
-
D.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
E.
typicalObservances
Indicates the customary practices, rituals, or activities that are commonly carried out in association with something (such as an event, tradition, or occasion).
- 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_69c008d8c61081908bcaf61510d881ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c068265a7481908571be7ea4ac11b7 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:33 p.m.