Triple
T36054546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morfin Gaunt |
E1042906
|
entity |
| Predicate | memoryStolenBy |
P184521
|
FINISHED |
| Object | Tom Marvolo Riddle |
—
|
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 Marvolo Riddle | Statement: [Morfin Gaunt, memoryStolenBy, Tom Marvolo Riddle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memoryStolenBy Context triple: [Morfin Gaunt, memoryStolenBy, Tom Marvolo Riddle]
-
A.
memoryHoleUsage
Indicates the extent to which information is being suppressed, erased, or obscured from records or awareness, as if discarded into a "memory hole."
-
B.
memoryPreservedBy
Indicates that a memory or information is maintained, retained, or kept intact through the action, mechanism, or influence of the associated entity.
-
C.
memoryState
Indicates the condition or configuration of an entity’s stored information at a particular point in time.
-
D.
memoryStrategy
Indicates the method or approach an entity uses to encode, store, or retrieve information from memory.
-
E.
memoryOverhead
Indicates the additional memory resources required by an entity or process beyond its essential or baseline memory usage.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b35e32d481909ef0220e6f6ff4a8 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2c66054819083897e25edb65ba7 |
completed | May 3, 2026, 8:40 p.m. |
Created at: May 3, 2026, 4:08 p.m.