Triple
T38593039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death Blossom |
E932496
|
entity |
| Predicate | userVulnerableDuringCast |
P167569
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Death Blossom, userVulnerableDuringCast, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userVulnerableDuringCast Context triple: [Death Blossom, userVulnerableDuringCast, true]
-
A.
vulnerableWhen
chosen
Indicates that an entity is at increased risk of harm, failure, or exploitation under certain specified conditions or circumstances.
-
B.
mayCast
Indicates that an entity has the permission or ability to perform a casting action on another entity or resource.
-
C.
canCastWhileBurrowed
Indicates that an entity is able to use or activate certain abilities or spells even while it is in a burrowed or underground state.
-
D.
capableOfCasting
Indicates that an entity has the ability or power to perform a particular casting action (such as casting a spell, role, or object).
-
E.
isVictimOf
Indicates that one entity suffers harm, loss, or wrongdoing as a result of another entity’s actions or events.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.