Triple
T33641893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Beast |
E861852
|
entity |
| Predicate | curseDeadline |
P89054
|
FINISHED |
| Object | before the last petal falls from the enchanted rose |
—
|
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: before the last petal falls from the enchanted rose | Statement: [the Beast, curseDeadline, before the last petal falls from the enchanted rose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curseDeadline Context triple: [the Beast, curseDeadline, before the last petal falls from the enchanted rose]
-
A.
timeOfCurse
chosen
Indicates the specific time at which a curse is cast, activated, or takes effect in relation to an entity or event.
-
B.
curseCondition
Indicates a condition or state in which an entity is affected by a curse or cursed effect.
-
C.
curseTrigger
Indicates that one entity causes, activates, or is responsible for initiating a curse that affects another entity.
-
D.
cursedToDieIn
Indicates that an entity is under a curse that causes them to die in a specified place or context.
-
E.
curseSymbol
Indicates that one entity serves as a symbol, sign, or representation of a curse associated with another entity.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:42 a.m.