Triple
T20843401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Completorium |
E513156
|
entity |
| Predicate | isTraditionallyPrayedAt |
P104221
|
FINISHED |
| Object | night |
—
|
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: night | Statement: [Completorium, isTraditionallyPrayedAt, night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTraditionallyPrayedAt Context triple: [Completorium, isTraditionallyPrayedAt, night]
-
A.
praysAt
Indicates that one entity performs an act of prayer at, or directed toward, a specific place or site.
-
B.
hasPrayerRite
Indicates that one entity is associated with, follows, or practices a particular prayer rite or liturgical form.
-
C.
canBePrayed
Indicates that an entity is a suitable or valid target for prayer or religious supplication.
-
D.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
-
E.
prayedDuring
chosen
Indicates that one entity performed prayer at some time within the duration of another specified event or time interval.
- 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_69e0b4f4898081908209e58edb8f9c45 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c34cdf9881909f3340874bbee5bc |
completed | April 21, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:43 p.m.