Triple
T30998993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regio III Isis et Serapis |
E789881
|
entity |
| Predicate | hasImportedCult |
P116737
|
FINISHED |
| Object | Egyptian mystery cults |
—
|
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: Egyptian mystery cults | Statement: [Regio III Isis et Serapis, hasImportedCult, Egyptian mystery cults]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImportedCult Context triple: [Regio III Isis et Serapis, hasImportedCult, Egyptian mystery cults]
-
A.
hasCultSince
Indicates that an entity has had an organized group of devoted followers (a cult) continuously since a specified time or date.
-
B.
hasAttestedCult
chosen
Indicates that an entity is known to have had an established, historically attested cult or formal worship practice.
-
C.
hasCultFeature
Indicates that an entity possesses a characteristic, attribute, or element associated with cultic or ritual practices.
-
D.
hasCultOrigin
Indicates that something originates from, or is derived from, a particular cult or cultic tradition.
-
E.
hasMainCult
Indicates that an entity is associated with a primary or predominant cult or religious worship tradition.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 29, 2026, 8:56 p.m.