Triple
T28527770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anaxibia |
E721952
|
entity |
| Predicate | notableFamilyCurse |
P7531
|
FINISHED |
| Object | curse of the House of Atreus |
—
|
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: curse of the House of Atreus | Statement: [Anaxibia, notableFamilyCurse, curse of the House of Atreus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFamilyCurse Context triple: [Anaxibia, notableFamilyCurse, curse of the House of Atreus]
-
A.
associatedCurse
chosen
Indicates that one entity is linked to, affected by, or bears responsibility for a particular curse related to another entity.
-
B.
originOfCurse
Indicates that one entity is the source or cause from which a particular curse originates or was created.
-
C.
typeOfCurse
Indicates that one entity is a specific kind or category of curse in relation to another entity.
-
D.
familyFate
Indicates a relationship where the outcome, destiny, or ultimate circumstances of one entity are determined by or closely tied to those of its family or familial group.
-
E.
hasSupernaturalConnectionWith
Indicates a special, non-natural bond or interaction exists between two entities that involves supernatural forces, powers, or phenomena.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a01295195748190b896d99c3d1f6134 |
completed | May 11, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_6a0128fe96dc8190a73715ab08752dd1 |
completed | May 11, 2026, 12:55 a.m. |
Created at: April 28, 2026, 3:26 a.m.