Triple
T28856138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalm 121 |
E728741
|
entity |
| Predicate | liturgicalLanguageUse |
P45911
|
FINISHED |
| Object | Hebrew |
—
|
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: Hebrew | Statement: [Psalm 121, liturgicalLanguageUse, Hebrew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalLanguageUse Context triple: [Psalm 121, liturgicalLanguageUse, Hebrew]
-
A.
liturgicalLanguageUsage
chosen
Indicates the relationship in which a particular language is used as the medium for conducting religious or liturgical rites, prayers, or ceremonies.
-
B.
liturgicalUsage
Indicates how something is used, practiced, or functions within a specific liturgical or worship context.
-
C.
liturgicalLanguageVersion
Indicates that one entity is a specific version or form of another entity expressed in a particular liturgical language.
-
D.
liturgicalUseFrequency
Indicates how often something is used or performed within a liturgical or worship context.
-
E.
liturgicalStyle
Indicates the manner or form of worship practice or ritual expression associated with a religious service or tradition.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a12d2e88190808480a0b77b1650 |
completed | May 2, 2026, 8:09 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:45 a.m.