Triple
T30498641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalm 57 |
E776076
|
entity |
| Predicate | divisionInPsalter |
P24139
|
FINISHED |
| Object | Book Two of Psalms |
—
|
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: Book Two of Psalms | Statement: [Psalm 57, divisionInPsalter, Book Two of Psalms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionInPsalter Context triple: [Psalm 57, divisionInPsalter, Book Two of Psalms]
-
A.
numberOfDivisionsInPsalter
Indicates the count of distinct divisions or sections within a given Psalter.
-
B.
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.
-
C.
priestlyDivision
Indicates a relationship where an individual is assigned to or associated with a specific priestly division or order within a religious hierarchy.
-
D.
numberOfPsalms
Indicates the total count of psalms associated with a given entity or context.
-
E.
psalmCollection
Indicates that one entity is a collection or compilation that contains or groups together psalms associated with another entity.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6877e57108190802c2adbbaf16d3c |
completed | May 2, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:14 p.m.