Triple
T30416346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Song of Ascents |
E773766
|
entity |
| Predicate | scripturalBookRange |
P21760
|
FINISHED |
| Object | Psalms 120–134 |
—
|
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: Psalms 120–134 | Statement: [Song of Ascents, scripturalBookRange, Psalms 120–134]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scripturalBookRange Context triple: [Song of Ascents, scripturalBookRange, Psalms 120–134]
-
A.
bookChapterRange
chosen
Indicates a relationship where a specified range of chapters within a book is identified or referenced as a contiguous segment.
-
B.
scripturalChapters
Indicates that one entity is composed of, contains, or is divided into the specified scriptural chapters.
-
C.
hasVerseRange
Indicates a relationship where a text or passage is associated with a specific contiguous range of verses it spans.
-
D.
scripturalSection
Indicates a relationship where one text or passage is a specific section or subdivision within a larger scriptural work.
-
E.
scriptureRead
Indicates that an entity reads, studies, or engages with a religious or sacred text.
- 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 29, 2026, 8:05 p.m.