Triple
T33205149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | erythema nodosum |
E849999
|
entity |
| Predicate | complicationRisk |
P124789
|
FINISHED |
| Object | postinflammatory hyperpigmentation |
—
|
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: postinflammatory hyperpigmentation | Statement: [erythema nodosum, complicationRisk, postinflammatory hyperpigmentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complicationRisk Context triple: [erythema nodosum, complicationRisk, postinflammatory hyperpigmentation]
-
A.
complicationType
chosen
Indicates the specific kind or category of complication associated with an event, condition, or process.
-
B.
complication
Indicates that one event, action, or condition makes another more difficult, problematic, or introduces an additional obstacle or entanglement in the situation.
-
C.
complicationFrequency
Indicates how often complications occur in relation to a given procedure, condition, or intervention.
-
D.
hasRiskFactorFor
Indicates that one entity contributes to or increases the likelihood of another entity experiencing a particular risk or adverse outcome.
-
E.
hasRiskFrom
Indicates that one entity is exposed to or may suffer potential harm, loss, or adverse effects as a result of 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: May 1, 2026, 1:30 a.m.