Triple
T36413301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ginny Weasley (possessed by Tom Riddle) |
E896938
|
entity |
| Predicate | lifeForceIsDrainedBy |
P90882
|
FINISHED |
| Object | Tom Riddle's memory |
—
|
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: Tom Riddle's memory | Statement: [Ginny Weasley (possessed by Tom Riddle), lifeForceIsDrainedBy, Tom Riddle's memory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifeForceIsDrainedBy Context triple: [Ginny Weasley (possessed by Tom Riddle), lifeForceIsDrainedBy, Tom Riddle's memory]
-
A.
lifeStageDamage
Indicates damage that occurs to or affects an entity during a specific stage of its life cycle.
-
B.
hasWeakness
Indicates that one entity is vulnerable to, or can be adversely affected or defeated by, another entity.
-
C.
effectOfDraining
chosen
Indicates the outcome or consequence that results from a draining process or action.
-
D.
damageEffect
Indicates that one entity causes harm, reduction, or deterioration to another entity or its properties.
-
E.
damageLeadsTo
Indicates that one instance of damage causally results in or contributes to another specified outcome or condition.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.