Triple
T36413305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ginny Weasley (possessed by Tom Riddle) |
E896938
|
entity |
| Predicate | diaryIsDestroyedWith |
P185467
|
FINISHED |
| Object | basilisk fang |
—
|
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: basilisk fang | Statement: [Ginny Weasley (possessed by Tom Riddle), diaryIsDestroyedWith, basilisk fang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diaryIsDestroyedWith Context triple: [Ginny Weasley (possessed by Tom Riddle), diaryIsDestroyedWith, basilisk fang]
-
A.
diaryIsDestroyedBy
chosen
Indicates that a diary is rendered unusable or ruined as a result of an action performed by another entity.
-
B.
destroyedFor
Indicates that one entity was ruined, eliminated, or rendered unusable specifically for the benefit, purpose, or objective of another entity.
-
C.
destroyedAfter
Indicates that one entity is destroyed at a point in time that occurs after the destruction of another entity.
-
D.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
E.
dateDestroyed
Indicates the specific date on which an entity was destroyed or ceased to exist.
- 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_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.