Triple
T31077251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ops |
E791998
|
entity |
| Predicate | ritualPosture |
P88144
|
FINISHED |
| Object | worshippers sat or knelt touching the ground |
—
|
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: worshippers sat or knelt touching the ground | Statement: [Ops, ritualPosture, worshippers sat or knelt touching the ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualPosture Context triple: [Ops, ritualPosture, worshippers sat or knelt touching the ground]
-
A.
positionOnRitual
chosen
Indicates the stance, role, or placement an entity holds with respect to a particular ritual or ceremonial practice.
-
B.
hasDeityPosture
Indicates the specific physical stance or pose attributed to a deity in a given context.
-
C.
ritualMovementBetween
Indicates a movement performed as part of a ritual that transitions or passes between two locations, participants, or ritual elements.
-
D.
ritualStructure
Indicates a relationship where an entity is a structure or built feature specifically used for performing rituals or ceremonial practices.
-
E.
partOfRitual
Indicates that an action, object, or event is included as a component or step within a larger ritual.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:02 p.m.