Triple
T31189419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalms 113–118 |
E795140
|
entity |
| Predicate | openingPsalm |
P104675
|
FINISHED |
| Object | Psalm 113 |
—
|
NE NERFINISHED |
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: Psalm 113 | Statement: [Psalms 113–118, openingPsalm, Psalm 113]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingPsalm Context triple: [Psalms 113–118, openingPsalm, Psalm 113]
-
A.
openingVerses
Indicates that one text or section contains the initial or introductory verses of another text or composition.
-
B.
openingVerseText
chosen
Indicates the specific text used as the opening verse of a work, performance, or section.
-
C.
openingVerseBy
Indicates that a work’s opening verse is authored, performed, or otherwise created by the specified entity.
-
D.
openingVerseType
Indicates the specific kind or category of an opening verse used at the beginning of a text, performance, or composition.
-
E.
openingHymnFor
Indicates that one item serves as the opening hymn for a particular event, service, or ceremony.
- 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 29, 2026, 9:08 p.m.