Triple
T13913484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of the Law |
E334556
|
entity |
| Predicate | roleInWorship |
P11534
|
FINISHED |
| Object | read publicly in assemblies |
—
|
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: read publicly in assemblies | Statement: [Book of the Law, roleInWorship, read publicly in assemblies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInWorship Context triple: [Book of the Law, roleInWorship, read publicly in assemblies]
-
A.
liturgicalRole
chosen
Indicates the specific function or position an entity holds within a religious or liturgical context.
-
B.
worshipperType
Indicates the specific category or kind of worshipper involved in a religious or devotional relationship or action.
-
C.
worshipLeadership
Indicates that one entity holds a leadership role or primary responsibility in organizing or guiding worship activities for another entity or group.
-
D.
worship
Indicates a relationship where one entity shows reverence, adoration, or religious devotion toward another entity, often recognizing it as sacred or divine.
-
E.
worshipLevel
Indicates the degree or intensity to which one entity reveres, honors, or performs acts of worship toward 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de27245c648190b2946845ce0fdbf8 |
completed | April 14, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.