Triple
T27328852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackson Lake |
E689734
|
entity |
| Predicate | memoryLossCause |
P59430
|
FINISHED |
| Object | Cybermen infostamp overload |
—
|
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: Cybermen infostamp overload | Statement: [Jackson Lake, memoryLossCause, Cybermen infostamp overload]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memoryLossCause Context triple: [Jackson Lake, memoryLossCause, Cybermen infostamp overload]
-
A.
memoryDeficit
Indicates a relationship where an entity exhibits an impairment or reduction in its ability to store, retain, or recall information.
-
B.
memoryResets
Indicates that an entity’s memory is cleared, reverted, or restarted, removing or resetting previously stored information.
-
C.
causedLossOf
chosen
Indicates that one entity brought about or was responsible for another entity experiencing a loss.
-
D.
memoryAffects
Indicates that one entity’s memory or recollection has an influence or impact on another entity or process.
-
E.
memoryState
Indicates the condition or configuration of an entity’s stored information at a particular point in time.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 11:37 a.m.