Triple
T31977722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ixion |
E816491
|
entity |
| Predicate | religiousTabooBroken |
P165915
|
FINISHED |
| Object | kin‑slaying |
—
|
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: kin‑slaying | Statement: [Ixion, religiousTabooBroken, kin‑slaying]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousTabooBroken Context triple: [Ixion, religiousTabooBroken, kin‑slaying]
-
A.
breaksTaboo
chosen
Indicates that an action or behavior violates a social, cultural, or moral taboo.
-
B.
reveredByReligion
Indicates that a religion holds a particular entity in high esteem, veneration, or sacred regard.
-
C.
tabooInTradition
Indicates that performing or engaging in the referenced action or relationship is considered forbidden or strongly disapproved of within a particular cultural or religious tradition.
-
D.
religiousConsequence
Indicates a relationship where one event, action, or state leads to an outcome specifically defined or understood in religious terms (such as divine reward, punishment, obligation, or spiritual effect).
-
E.
namedAfterReligion
Indicates that an entity’s name is derived from or inspired by a particular religion or religious 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: May 1, 2026, 12:11 a.m.