Triple
T7199864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concluding Rites |
E168711
|
entity |
| Predicate | hasLiturgicalGesture |
P28177
|
FINISHED |
| Object | bow |
—
|
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: bow | Statement: [Concluding Rites, hasLiturgicalGesture, bow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiturgicalGesture Context triple: [Concluding Rites, hasLiturgicalGesture, bow]
-
A.
liturgicalGesture
chosen
Indicates a ritual bodily movement or posture performed as part of a religious or liturgical practice.
-
B.
hasLiturgicalPosture
Indicates that an entity is associated with a specific bodily posture or position used in a liturgical or religious ritual context.
-
C.
hasLiturgicalSymbol
Indicates that one entity serves as a liturgical symbol or emblem associated with another entity within a religious or worship context.
-
D.
hasLiturgicalExpression
Indicates that one entity expresses, embodies, or is manifested through the liturgical practices, rites, or worship forms of another entity.
-
E.
hasLiturgicalNature
Indicates that something possesses a liturgical character or function, typically relating to formal religious worship or rites.
- 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6e92cc8ac8190a6448b79496a8249 |
completed | March 27, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69c6e757fed4819091b0a096e3befc3a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:52 p.m.