Triple
T34563752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maleva |
E887415
|
entity |
| Predicate | explainsCurseTo |
P179315
|
FINISHED |
| Object | Larry Talbot |
—
|
NE NERFINISHED |
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: Larry Talbot | Statement: [Maleva, explainsCurseTo, Larry Talbot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explainsCurseTo Context triple: [Maleva, explainsCurseTo, Larry Talbot]
-
A.
associatedCurse
Indicates that one entity is linked to, affected by, or bears responsibility for a particular curse related to another entity.
-
B.
reasonForCurse
Indicates the cause, justification, or triggering event that led to a curse being placed on someone or something.
-
C.
curseSymbol
Indicates that one entity serves as a symbol, sign, or representation of a curse associated with another entity.
-
D.
curseTrigger
Indicates that one entity causes, activates, or is responsible for initiating a curse that affects another entity.
-
E.
curseCondition
Indicates a condition or state in which an entity is affected by a curse or cursed effect.
- F. None of above. chosen
Provenance (4 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_69f349d0c4d881908dd0950f5eb9ec0a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720653cf081908a28d5419d4cb1a8 |
completed | May 3, 2026, 10:16 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: May 1, 2026, 2:02 a.m.