Triple
T7832261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalm 107:23 |
E181600
|
entity |
| Predicate | positionInPsalm |
P24139
|
FINISHED |
| Object | beginning of the seafarers section of Psalm 107 |
—
|
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: beginning of the seafarers section of Psalm 107 | Statement: [Psalm 107:23, positionInPsalm, beginning of the seafarers section of Psalm 107]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInPsalm Context triple: [Psalm 107:23, positionInPsalm, beginning of the seafarers section of Psalm 107]
-
A.
positionInVerse
Indicates the specific ordinal location that something occupies within a verse.
-
B.
psalmNumber
Indicates the specific numerical designation assigned to a psalm within an ordered collection or canon.
-
C.
positionInBible
Indicates the specific location or order of a passage, verse, or book within the structured sequence of the Bible.
-
D.
psalmUsed
Indicates that one entity makes use of, references, or incorporates a particular psalm in some context or activity.
-
E.
functionInPsalter
chosen
Indicates the specific liturgical, structural, or thematic role that a psalm (or part of it) serves within the overall collection of the Psalter.
- 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_69ca8284a25c8190a1a20afad30da792 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb0648bb308190a34fbcd81ff6fda2 |
completed | March 30, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:45 p.m.