Triple
T26828943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalm 130 |
E675442
|
entity |
| Predicate | positionInPsalms |
P94954
|
FINISHED |
| Object | One of the Songs of Ascents (Psalms 120–134) |
—
|
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: One of the Songs of Ascents (Psalms 120–134) | Statement: [Psalm 130, positionInPsalms, One of the Songs of Ascents (Psalms 120–134)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInPsalms Context triple: [Psalm 130, positionInPsalms, One of the Songs of Ascents (Psalms 120–134)]
-
A.
positionInBible
Indicates the specific location or order of a passage, verse, or book within the structured sequence of the Bible.
-
B.
positionInHebrewBible
Indicates the ordinal position that something occupies within the canonical sequence of books or passages in the Hebrew Bible.
-
C.
positionInScripture
chosen
Indicates the specific location or ordering of a passage, verse, or element within a scriptural text.
-
D.
psalmNumber
Indicates the specific numerical designation assigned to a psalm within an ordered collection or canon.
-
E.
positionInVerse
Indicates the specific ordinal location that something occupies within a verse.
- 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 27, 2026, 5 a.m.