Triple
T19154690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daily Offering |
E468901
|
entity |
| Predicate | includesOfferingOf |
P57109
|
FINISHED |
| Object | prayers |
—
|
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: prayers | Statement: [Daily Offering, includesOfferingOf, prayers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesOfferingOf Context triple: [Daily Offering, includesOfferingOf, prayers]
-
A.
hasOffering
chosen
Indicates that one entity provides, presents, or makes available an offering (such as a product, service, or item) to another entity or context.
-
B.
usesOffering
Indicates that one entity makes use of, applies, or relies on a particular offering provided by another entity.
-
C.
isOfferedBy
Indicates that a service, product, or opportunity is provided or made available by a particular entity.
-
D.
associatedOffering
Indicates a relationship where one offering is linked or connected to another offering as related or contextually relevant.
-
E.
usedAsOfferingAt
Indicates that something is employed or presented as an offering in a particular context, place, or event.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eeb81bf08190b0352137eb4a5763 |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.