Triple
T21787845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Molaison |
E537886
|
entity |
| Predicate | memoryPreserved |
P113620
|
FINISHED |
| Object | short-term memory |
—
|
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: short-term memory | Statement: [Henry Molaison, memoryPreserved, short-term memory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memoryPreserved Context triple: [Henry Molaison, memoryPreserved, short-term memory]
-
A.
memoryPreservedBy
Indicates that a memory or information is maintained, retained, or kept intact through the action, mechanism, or influence of the associated entity.
-
B.
memoryState
chosen
Indicates the condition or configuration of an entity’s stored information at a particular point in time.
-
C.
preservedFor
Indicates that something has been kept intact or maintained in a particular state for the benefit, use, or reference of a specified entity or purpose.
-
D.
memoryResets
Indicates that an entity’s memory is cleared, reverted, or restarted, removing or resetting previously stored information.
-
E.
somePreservedAs
Indicates that at least one part or instance of an entity is kept or maintained in a particular state, form, 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0621c68588190977891055e80a499 |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:52 p.m.