Triple
T18806168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munchausen syndrome by proxy |
E459878
|
entity |
| Predicate | diagnosisIsDifficult |
P133492
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Munchausen syndrome by proxy, diagnosisIsDifficult, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diagnosisIsDifficult Context triple: [Munchausen syndrome by proxy, diagnosisIsDifficult, yes]
-
A.
diagnoses
Indicates that a medical professional identifies and determines the nature or cause of a condition, disease, or problem in a patient.
-
B.
diagnosisMethod
Indicates the method, procedure, or technique used to establish or confirm a diagnosis for a condition or case.
-
C.
differentialDiagnosisIncludes
Indicates that a differential diagnosis list for a case or condition contains a particular possible diagnosis as one of the considered alternatives.
-
D.
diagnosisDate
Indicates the date on which a diagnosis was formally established or recorded for an entity.
-
E.
diagnosedWith
Indicates that a subject has been identified, typically by a medical professional, as having a particular disease or medical condition.
- F. None of above. chosen
Provenance (4 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a3d7f8d08190a3e02fab6dc40bb5 |
completed | April 20, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49a9bcc0c81908df3e513fd6762ff |
completed | April 19, 2026, 9:04 a.m. |
Created at: April 10, 2026, 11:53 a.m.