Triple
T27605594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Ingram |
E700169
|
entity |
| Predicate | caseImpactOn |
P125238
|
FINISHED |
| Object | public understanding of memory reliability |
—
|
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: public understanding of memory reliability | Statement: [Paul Ingram, caseImpactOn, public understanding of memory reliability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseImpactOn Context triple: [Paul Ingram, caseImpactOn, public understanding of memory reliability]
-
A.
canImpact
chosen
Indicates that one entity has the potential or ability to affect, influence, or cause a change in another entity.
-
B.
exportImpact
Indicates the effect or consequences that an entity’s exports have on another entity, system, or context.
-
C.
impactDescription
Indicates a description of the effect, consequence, or influence that one entity, action, or event has on another.
-
D.
impactStatus
Indicates the current state or condition of how something has affected or influenced a target.
-
E.
recognizesImpactOn
Indicates that one entity acknowledges or understands the effect or consequences it has on another entity or situation.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6309aa494819092c2b02bd6adaeb6 |
completed | May 2, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:09 p.m.