Triple
T5125099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orphic Hymns |
E115564
|
entity |
| Predicate | primaryDeitiesInvoked |
P16947
|
FINISHED |
| Object | Olympian gods |
—
|
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: Olympian gods | Statement: [Orphic Hymns, primaryDeitiesInvoked, Olympian gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDeitiesInvoked Context triple: [Orphic Hymns, primaryDeitiesInvoked, Olympian gods]
-
A.
mainDeity
Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
-
B.
servedDeity
Indicates that one entity acted in service, devotion, or worship toward a particular deity.
-
C.
otherDeity
Indicates that one deity is distinct from and not identical to another deity within a given context or system.
-
D.
involvesDeity
chosen
Indicates that the situation, event, or concept has the participation, presence, or relevance of a deity as a central element of the relationship.
-
E.
integratesDeity
Indicates that one entity incorporates, assimilates, or unifies a deity or divine aspect into itself or into a larger 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_69bd4442ade0819087b9461f892b206b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77aa68b88190a50dd736a72d2901 |
completed | March 20, 2026, 4:36 p.m. |
Created at: March 20, 2026, 1:42 p.m.