Triple
T32706886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctuary of Juno Sospita |
E836296
|
entity |
| Predicate | hasDeityCultTitleMeaning |
P124236
|
FINISHED |
| Object | the Saviour |
—
|
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: the Saviour | Statement: [Sanctuary of Juno Sospita, hasDeityCultTitleMeaning, the Saviour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeityCultTitleMeaning Context triple: [Sanctuary of Juno Sospita, hasDeityCultTitleMeaning, the Saviour]
-
A.
hasCultEpithetOfDeity
chosen
Indicates that a specific cult epithet or title is associated with, or used for, a particular deity.
-
B.
hasTypeOfDeityCult
Indicates that an entity is associated with, practices, or maintains a cult devoted to a particular type or category of deity.
-
C.
hasSignificanceForDeity
Indicates that something holds particular importance, value, or meaning in relation to a specific deity.
-
D.
hasCultTitle
Indicates that an entity is known by or associated with a specific cult-related title or honorific.
-
E.
worshippedDeityCulture
Indicates that a particular culture reveres, honors, or practices religious devotion toward a specific deity.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
Created at: May 1, 2026, 1:10 a.m.