Triple
T36413304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ginny Weasley (possessed by Tom Riddle) |
E896938
|
entity |
| Predicate | diaryIsDestroyedBy |
P185467
|
FINISHED |
| Object | Harry Potter |
—
|
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: Harry Potter | Statement: [Ginny Weasley (possessed by Tom Riddle), diaryIsDestroyedBy, Harry Potter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diaryIsDestroyedBy Context triple: [Ginny Weasley (possessed by Tom Riddle), diaryIsDestroyedBy, Harry Potter]
-
A.
destroyedFor
Indicates that one entity was ruined, eliminated, or rendered unusable specifically for the benefit, purpose, or objective of another entity.
-
B.
destroyedAfter
Indicates that one entity is destroyed at a point in time that occurs after the destruction of another entity.
-
C.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
D.
dateDestroyed
Indicates the specific date on which an entity was destroyed or ceased to exist.
-
E.
destroyedInText
Indicates that one entity is described as being destroyed within the content or narrative of a given text.
- 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_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. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:10 p.m.