Triple
T5091637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | God’s Gardeners |
E114763
|
entity |
| Predicate | scriptureForm |
P6836
|
FINISHED |
| Object | sermons |
—
|
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: sermons | Statement: [God’s Gardeners, scriptureForm, sermons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptureForm Context triple: [God’s Gardeners, scriptureForm, sermons]
-
A.
scriptureFor
Indicates that one entity serves as a scriptural or authoritative religious text for another entity (such as a person, group, or belief system).
-
B.
scriptureType
chosen
Indicates the classification or category of a scripture in relation to its type or genre.
-
C.
inScripture
Indicates that something is mentioned, described, or referenced within a scriptural or sacred text.
-
D.
scripturalCorpus
Indicates that one entity is a body of scriptural or sacred texts associated with, or serving as the canonical writings for, another entity.
-
E.
receivedScripture
Indicates that one entity has been given or accepted a body of sacred or authoritative religious writings from another source.
- 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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7541b2bc8190b58c2a23733b7825 |
completed | March 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69bd715c0a448190afc837c6c31dc6ab |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.