Triple
T36349444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remember Sammy Jankis |
E895154
|
entity |
| Predicate | refersToCondition |
P44268
|
FINISHED |
| Object | anterograde amnesia |
—
|
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: anterograde amnesia | Statement: [Remember Sammy Jankis, refersToCondition, anterograde amnesia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToCondition Context triple: [Remember Sammy Jankis, refersToCondition, anterograde amnesia]
-
A.
containsCondition
Indicates that one entity includes, embodies, or is associated with a particular condition.
-
B.
targetedCondition
Indicates that an action, intervention, or entity is specifically directed toward affecting, treating, or addressing a particular condition.
-
C.
resultCondition
Indicates the condition, state, or outcome that holds true as a result of a preceding action, event, or process.
-
D.
conditionRelatesTo
Indicates that one condition is relevant, connected, or applicable to another condition or contextual factor.
-
E.
refersSpecificallyTo
chosen
Indicates that one entity makes an explicit, precise reference to another particular entity, distinguishing it from more general or ambiguous references.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: May 3, 2026, 4:09 p.m.