Triple
T14002750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valerie Harper |
E336869
|
entity |
| Predicate | announcedCancerDiagnosis |
P4650
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Valerie Harper, announcedCancerDiagnosis, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedCancerDiagnosis Context triple: [Valerie Harper, announcedCancerDiagnosis, 2013]
-
A.
diagnosedWith
Indicates that a subject has been identified, typically by a medical professional, as having a particular disease or medical condition.
-
B.
isTerminallyIll
Indicates that an entity is suffering from an incurable illness expected to lead to death in the relatively near future.
-
C.
announcedThat
chosen
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
-
D.
averageSurvivalAfterDiagnosis
Indicates the typical length of time individuals survive following the point at which a condition or disease is first diagnosed.
-
E.
announcedFor
Indicates that one entity has been publicly declared or made known in connection with, or on behalf of, another 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed06a50819093ddc64f55050689 |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:19 p.m.