Triple
T16437485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Hoppus |
E399213
|
entity |
| Predicate | announcedCancerRemission |
P4650
|
FINISHED |
| Object | 2021-09 |
—
|
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: 2021-09 | Statement: [Mark Hoppus, announcedCancerRemission, 2021-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedCancerRemission Context triple: [Mark Hoppus, announcedCancerRemission, 2021-09]
-
A.
survivedDisease
Indicates that an entity successfully lived through and recovered from a specified disease.
-
B.
curedWith
Indicates that one entity is treated or healed by using another entity as the remedy or therapeutic method.
-
C.
remainsRecoveredFrom
Indicates that physical remains of an entity have been found and retrieved from a specified source, location, or context.
-
D.
announcedThat
chosen
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
-
E.
recoveredWithAidFrom
Indicates that an entity returned to a prior or improved state (such as health, function, or condition) as a result of assistance, intervention, or support from 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ba49f3481908e7ea62467ef5813 |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.