Triple
T9362940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalm 113 |
E225322
|
entity |
| Predicate | bookOrderInHebrewBible |
P6325
|
FINISHED |
| Object | in the third section (Writings) |
—
|
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: in the third section (Writings) | Statement: [Psalm 113, bookOrderInHebrewBible, in the third section (Writings)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bookOrderInHebrewBible Context triple: [Psalm 113, bookOrderInHebrewBible, in the third section (Writings)]
-
A.
bookOrderInPsalms
Indicates the sequential position of a psalm within the ordered collection of psalms in the biblical book.
-
B.
positionInHebrewBible
chosen
Indicates the ordinal position that something occupies within the canonical sequence of books or passages in the Hebrew Bible.
-
C.
includesMegillot
Indicates that one entity contains or encompasses the set of texts or items referred to as Megillot.
-
D.
bookOrderInMinorProphets
Indicates the relative ordering of books within the collection traditionally known as the Minor Prophets.
-
E.
subsectionOfTanakh
Indicates that one text division is a recognized subsection within the larger structure of the Tanakh.
- 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_69ca842bdd648190904131d58620d448 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd503ddf8c81908b090afa54ec5e6d |
completed | April 1, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69cc7a6abb8c81908c7a2f4ee92cc949 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:42 p.m.