Triple
T7487127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dimalik |
E176908
|
entity |
| Predicate | worshipInvolves |
P11149
|
FINISHED |
| Object | household rituals |
—
|
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: household rituals | Statement: [Dimalik, worshipInvolves, household rituals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipInvolves Context triple: [Dimalik, worshipInvolves, household rituals]
-
A.
worship
Indicates a relationship where one entity shows reverence, adoration, or religious devotion toward another entity, often recognizing it as sacred or divine.
-
B.
worshipType
chosen
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
-
C.
worshipImplication
Indicates that one entity’s worship, reverence, or devotional behavior toward another implies or entails a particular belief, status, or relationship between them.
-
D.
worshipScope
Indicates the range or extent within which worship, veneration, or religious devotion is directed or practiced.
-
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_69c69f24ac508190bb98fe927c0bd065 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5582adc81908b68439762965d88 |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:43 p.m.