Triple
T36182453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Binx |
E1046751
|
entity |
| Predicate | endsCurseWhen |
P89054
|
FINISHED |
| Object | Sanderson sisters are defeated |
—
|
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: Sanderson sisters are defeated | Statement: [Binx, endsCurseWhen, Sanderson sisters are defeated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endsCurseWhen Context triple: [Binx, endsCurseWhen, Sanderson sisters are defeated]
-
A.
curseCondition
Indicates a condition or state in which an entity is affected by a curse or cursed effect.
-
B.
associatedCurse
Indicates that one entity is linked to, affected by, or bears responsibility for a particular curse related to another entity.
-
C.
curseTrigger
Indicates that one entity causes, activates, or is responsible for initiating a curse that affects another entity.
-
D.
attemptedCurseReversal
Indicates an action where one entity tried, but did not necessarily succeed, to reverse or undo a curse affecting another entity.
-
E.
timeOfCurse
chosen
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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.