Triple
T19570200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark of Cain |
E489687
|
entity |
| Predicate | relatedMythicMotive |
P9595
|
FINISHED |
| Object | protective curse |
—
|
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: protective curse | Statement: [Mark of Cain, relatedMythicMotive, protective curse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedMythicMotive Context triple: [Mark of Cain, relatedMythicMotive, protective curse]
-
A.
associatedMystic
Indicates a relationship where one entity is linked or connected to another through a mystical, spiritual, or esoteric association.
-
B.
relatedMythicalPlace
Indicates that one entity has an association or connection with a mythical or legendary place in relation to the other entity.
-
C.
relatedMythicalPlace
Indicates that one entity has an association or connection with a mythical or legendary place represented by the other entity.
-
D.
linkedToMythology
chosen
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
E.
sharesMythosWith
Indicates that two entities are associated with, or originate from, the same mythological tradition, narrative system, or shared set of myths.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6402043588190a99f5a55c5dcd8a6 |
completed | April 20, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.