Triple
T3948595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cassandra |
E84806
|
entity |
| Predicate | causeOfCurse |
P694
|
FINISHED |
| Object | rejected Apollo’s advances |
—
|
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: rejected Apollo’s advances | Statement: [Cassandra, causeOfCurse, rejected Apollo’s advances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfCurse Context triple: [Cassandra, causeOfCurse, rejected Apollo’s advances]
-
A.
associatedCurse
Indicates that one entity is linked to, affected by, or bears responsibility for a particular curse related to another entity.
-
B.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
C.
attemptedCurseReversal
Indicates an action where one entity tried, but did not necessarily succeed, to reverse or undo a curse affecting another entity.
-
D.
scripturalCurse
Indicates that one entity pronounces or embodies a curse upon another as recorded or prescribed in a religious or scriptural context.
-
E.
causeOfDownfall
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
- 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_69aed934fbfc8190847068e4546de963 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaa5afdc8190b709af2473d75d02 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8ed04e4819096bced8971cd888d |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:30 p.m.