Triple
T1094932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalm 119 |
E24250
|
entity |
| Predicate | positionInBookOfPsalms |
P18696
|
FINISHED |
| Object | 119 |
—
|
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: 119 | Statement: [Psalm 119, positionInBookOfPsalms, 119]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInBookOfPsalms Context triple: [Psalm 119, positionInBookOfPsalms, 119]
-
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.
positionAmongGospels
Indicates the numerical order or placement of a given gospel within the sequence of all gospels.
-
D.
positionInTanakh
Indicates the relative location or ordering of a text or passage within the canonical structure of the Tanakh.
-
E.
verseNumber
chosen
Indicates the specific numbered position of a verse within an ordered sequence, such as in a chapter, song, or poem.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b99e92308190b8a8c499e1630672 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b743175481908f3967e589717c55 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.