Triple
T16848142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Big C |
E409597
|
entity |
| Predicate | protagonistMedicalCondition |
P93885
|
FINISHED |
| Object | terminal cancer |
—
|
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: terminal cancer | Statement: [The Big C, protagonistMedicalCondition, terminal cancer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistMedicalCondition Context triple: [The Big C, protagonistMedicalCondition, terminal cancer]
-
A.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
B.
mainPatientInStory
Indicates that an entity is the primary patient or central medical subject around which the story or narrative is focused.
-
C.
hasProtagonistCondition
chosen
Indicates that the main character in a narrative has a particular condition, state, or affliction.
-
D.
protagonistType
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
E.
protagonistMust
Indicates that a particular entity is required to serve as the main character or central focus within a narrative or scenario.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b376bac48190ae09f29a28c55f8c |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.