Triple
T5955425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalm 84 |
E132500
|
entity |
| Predicate | scriptureCitationFormat |
P67049
|
FINISHED |
| Object | Ps 84 |
—
|
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: Ps 84 | Statement: [Psalm 84, scriptureCitationFormat, Ps 84]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptureCitationFormat Context triple: [Psalm 84, scriptureCitationFormat, Ps 84]
-
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
Indicates the classification or category of a scripture in relation to its type or genre.
-
C.
recognizesScripturesFrom
Indicates that one entity acknowledges or accepts certain scriptures as authoritative or valid based on another entity as their source or origin.
-
D.
canonizedScriptureIn
Indicates that a text or scripture has been formally recognized and included as canonical within a particular religious tradition, community, or collection.
-
E.
scripturalCorpus
Indicates that one entity is a body of scriptural or sacred texts associated with, or serving as the canonical writings for, another entity.
- F. None of above. chosen
Provenance (4 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_69c0086b05cc8190a8f36a96927a525c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03fb7f8a88190a8bd45208bda4a03 |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0335a635881909c58c1ef0f97f1e8 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c03fb6bb7c81909c5629fba408dc69 |
completed | March 22, 2026, 7:15 p.m. |
Created at: March 22, 2026, 4:02 p.m.