Triple
T5742964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aguirre |
E126658
|
entity |
| Predicate | curseStatus |
P62729
|
FINISHED |
| Object | cursed to immortality |
—
|
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: cursed to immortality | Statement: [Aguirre, curseStatus, cursed to immortality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curseStatus Context triple: [Aguirre, curseStatus, cursed to immortality]
-
A.
associatedCurse
Indicates that one entity is linked to, affected by, or bears responsibility for a particular curse related to another entity.
-
B.
attemptedCurseReversal
Indicates an action where one entity tried, but did not necessarily succeed, to reverse or undo a curse affecting another entity.
-
C.
magicalStatus
chosen
Indicates that an entity possesses, is affected by, or is characterized in terms of a particular magical condition or property.
-
D.
scripturalCurse
Indicates that one entity pronounces or embodies a curse upon another as recorded or prescribed in a religious or scriptural context.
-
E.
cultStatus
Indicates that something has achieved a devoted, niche following or admiration that is disproportionate to its mainstream popularity.
- 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_69c0083179548190b384b0bf3c08ca4d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021ca61688190875bd6107161c284 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.