Triple
T14484387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Rank |
E359189
|
entity |
| Predicate | illnessCause |
P61998
|
FINISHED |
| Object | consequence of his father’s debauchery |
—
|
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: consequence of his father’s debauchery | Statement: [Dr. Rank, illnessCause, consequence of his father’s debauchery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: illnessCause Context triple: [Dr. Rank, illnessCause, consequence of his father’s debauchery]
-
A.
causeOfIllness
chosen
Indicates that one entity is the reason or source responsible for another entity’s illness or disease.
-
B.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
C.
illness
Indicates that an entity is affected by, or suffering from, a particular disease or medical condition.
-
D.
primaryCauseCategory
Indicates the main type or classification of cause responsible for an outcome or event.
-
E.
settingOfIllness
Indicates the context, environment, or circumstances in which an illness occurs or manifests.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924d7f4c8190b1f62b5ffe1ff649 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.