Triple
T6413332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hecate’s Deipnon |
E127761
|
entity |
| Predicate | associatedDeityAspect |
P57193
|
FINISHED |
| Object | Hecate as goddess of crossroads |
—
|
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: Hecate as goddess of crossroads | Statement: [Hecate’s Deipnon, associatedDeityAspect, Hecate as goddess of crossroads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDeityAspect Context triple: [Hecate’s Deipnon, associatedDeityAspect, Hecate as goddess of crossroads]
-
A.
attributeOfDeity
chosen
Indicates that something is a characteristic, quality, or property belonging to a deity.
-
B.
depictedWithDeity
Indicates that an entity is shown or represented together with a particular deity in some form of depiction.
-
C.
relatedNameOfGod
Indicates that one entity is a name, title, or designation that refers to or is associated with God.
-
D.
relationshipToDeities
Indicates how an entity is connected or related to one or more deities, such as through worship, lineage, role, or status.
-
E.
worshippedAlongside
Indicates that two deities or sacred figures were venerated together within the same religious context, ritual, or cult practice.
- 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068e5187c8190a6be1b934e0f1b3a |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:42 p.m.