Triple
T31152056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Wheelwright |
E794100
|
entity |
| Predicate | hasStrongMemoryOf |
P145824
|
FINISHED |
| Object | Owen Meany’s voice |
—
|
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: Owen Meany’s voice | Statement: [John Wheelwright, hasStrongMemoryOf, Owen Meany’s voice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrongMemoryOf Context triple: [John Wheelwright, hasStrongMemoryOf, Owen Meany’s voice]
-
A.
hasMemoryIn
Indicates that an entity possesses or stores memory, information, or experiences within a specified context, location, or medium.
-
B.
retainsMemoriesOf
chosen
Indicates that one entity continues to hold or preserve memories about another entity or about events involving that entity.
-
C.
rememberedFor
Indicates that one entity is known or recognized primarily because of, or in association with, another entity or achievement.
-
D.
hasUserMemory
Indicates that an entity maintains or is associated with stored information about a specific user.
-
E.
memorizedBy
Indicates that some content, information, or material has been learned and retained in memory by a particular entity.
- 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_69f224d41bb48190a5621cd1485e3a30 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: April 29, 2026, 9:06 p.m.