Triple
T3001744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suffering of Zion |
E81802
|
entity |
| Predicate | scripturalGenre |
P6836
|
FINISHED |
| Object | lamentation literature |
—
|
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: lamentation literature | Statement: [Suffering of Zion, scripturalGenre, lamentation literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scripturalGenre Context triple: [Suffering of Zion, scripturalGenre, lamentation literature]
-
A.
scriptureType
chosen
Indicates the classification or category of a scripture in relation to its type or genre.
-
B.
scripturalTheme
Indicates that one entity represents a central religious or theological theme expressed, discussed, or emphasized within a scriptural text or passage.
-
C.
liturgicalGenre
Indicates the specific type or category of liturgical text, music, or ritual to which something belongs.
-
D.
scriptureFor
Indicates that one entity serves as a scriptural or authoritative religious text for another entity (such as a person, group, or belief system).
-
E.
religiousGenre
Indicates that the subject is associated with or categorized under a religious genre, style, 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_69ad8b1c4de88190a83b7cefaa1f2842 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a11b4bc81909ce06121361b4e0f |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.