Triple
T19133596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Στύξ |
E468377
|
entity |
| Predicate | consequenceOfOathBreaking |
P64962
|
FINISHED |
| Object | divine punishment |
—
|
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: divine punishment | Statement: [Στύξ, consequenceOfOathBreaking, divine punishment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceOfOathBreaking Context triple: [Στύξ, consequenceOfOathBreaking, divine punishment]
-
A.
penaltyForBreakingOath
chosen
Indicates the punishment or negative consequence imposed when an oath is violated.
-
B.
exceptionToOaths
Indicates that a situation, condition, or rule provides a valid exception to an otherwise binding oath or sworn obligation.
-
C.
oath
Indicates a formal, binding promise or pledge made by one party to uphold certain duties, truths, or obligations, often under conditions of solemnity or authority.
-
D.
oathsAbout
Indicates that one entity makes or concerns a formal oath regarding another entity or subject.
-
E.
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).
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3eb325081909035beefd1c9daf0 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.