Triple
T24777611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chupwalas |
E619904
|
entity |
| Predicate | religionOrCult |
P102165
|
FINISHED |
| Object | Cult of Silence |
—
|
NE NERFINISHED |
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: Cult of Silence | Statement: [Chupwalas, religionOrCult, Cult of Silence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionOrCult Context triple: [Chupwalas, religionOrCult, Cult of Silence]
-
A.
typeOfCult
Indicates that one entity is a specific kind or category of cult relative to another entity.
-
B.
religionOrBelief
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
-
C.
otherReligion
Indicates that one entity follows or is associated with a religion that is different from the religion of another entity.
-
D.
ethnicReligion
Indicates that a religion is closely associated with a particular ethnic group, often tied to that group’s culture, ancestry, or identity.
-
E.
associatedReligionOrBelief
chosen
Indicates that an entity is connected to, identified with, or characterized by a particular religion or belief system.
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:41 a.m.