Triple
T26530593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kundry |
E670809
|
entity |
| Predicate | cursedFor |
P7531
|
FINISHED |
| Object | laughing at Christ on the cross |
—
|
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: laughing at Christ on the cross | Statement: [Kundry, cursedFor, laughing at Christ on the cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cursedFor Context triple: [Kundry, cursedFor, laughing at Christ on the cross]
-
A.
cursedToDieIn
Indicates that an entity is under a curse that causes them to die in a specified place or context.
-
B.
cursedIdentityOf
Indicates that one entity is the cursed or negatively transformed identity or form of another entity.
-
C.
associatedCurse
chosen
Indicates that one entity is linked to, affected by, or bears responsibility for a particular curse related to another entity.
-
D.
curseCondition
Indicates a condition or state in which an entity is affected by a curse or cursed effect.
-
E.
timeOfCurse
Indicates the specific time at which a curse is cast, activated, or takes effect in relation to an entity or event.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613f746248190b9ef77cb0eece781 |
completed | May 2, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:35 a.m.