Triple
T15470974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bendis |
E376657
|
entity |
| Predicate | natureOfCult |
P27555
|
FINISHED |
| Object | orgiastic elements |
—
|
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: orgiastic elements | Statement: [Bendis, natureOfCult, orgiastic elements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: natureOfCult Context triple: [Bendis, natureOfCult, orgiastic elements]
-
A.
typeOfCult
Indicates that one entity is a specific kind or category of cult relative to another entity.
-
B.
typeOfCultObject
Indicates that one entity is the specific kind or category of cult object to which the other entity belongs or is classified.
-
C.
centerOfCult
Indicates that the subject functions as the primary focus or core figure around which a cult is organized or devoted.
-
D.
religiousNature
chosen
Indicates that something possesses a religious character, quality, or orientation, such as being related to faith, worship, doctrine, or spiritual practice.
-
E.
countryOfCult
Indicates that a particular cult, religious group, or worship practice is associated with, originates from, or is primarily practiced in a specific country.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f6b49788190b270fdfe92646842 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:33 a.m.