Triple
T3028166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo slaying Python |
E82829
|
entity |
| Predicate | associatedRite |
P11123
|
FINISHED |
| Object | purification rituals for Apollo |
—
|
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: purification rituals for Apollo | Statement: [Apollo slaying Python, associatedRite, purification rituals for Apollo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRite Context triple: [Apollo slaying Python, associatedRite, purification rituals for Apollo]
-
A.
associatedWithSacrament
Indicates a relationship where something is connected or related to a specific sacrament in a religious or ritual context.
-
B.
observedInRite
Indicates that an entity participates in or is witnessed as part of a specific ritual or ceremonial practice.
-
C.
associatedCult
Indicates that an entity is connected or linked to a particular cult, typically through membership, affiliation, or influence.
-
D.
containsRite
Indicates that one entity includes or incorporates a specific rite as part of its structure, content, or practice.
-
E.
notableRite
chosen
Indicates that an entity is associated with a significant or distinguished ritual, ceremony, or formal rite.
- 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9abea8f4819090554d7319778170 |
completed | March 8, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69ad961e2a408190afb1759132701305 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.