Triple
T31540835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Charlotte of Belgium |
E804742
|
entity |
| Predicate | chronicallyIllWith |
P129457
|
FINISHED |
| Object | mental illness |
—
|
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: mental illness | Statement: [Princess Charlotte of Belgium, chronicallyIllWith, mental illness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronicallyIllWith Context triple: [Princess Charlotte of Belgium, chronicallyIllWith, mental illness]
-
A.
isTerminallyIll
Indicates that an entity is suffering from an incurable illness expected to lead to death in the relatively near future.
-
B.
diagnosedWith
Indicates that a subject has been identified, typically by a medical professional, as having a particular disease or medical condition.
-
C.
settingOfIllness
Indicates the context, environment, or circumstances in which an illness occurs or manifests.
-
D.
illness
Indicates that an entity is affected by, or suffering from, a particular disease or medical condition.
-
E.
clinicalCondition
chosen
Indicates that one entity has, exhibits, or is associated with a particular medical or health-related condition described by the other 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 30, 2026, 10:06 p.m.