Triple
T2601825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vorkuta camps |
E58359
|
entity |
| Predicate | healthConditions |
P4720
|
FINISHED |
| Object | widespread disease |
—
|
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: widespread disease | Statement: [Vorkuta camps, healthConditions, widespread disease]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healthConditions Context triple: [Vorkuta camps, healthConditions, widespread disease]
-
A.
conditions
Indicates that one entity specifies or imposes requirements, constraints, or circumstances that must be satisfied or hold true for another entity or situation.
-
B.
healthEffect
Indicates the impact or consequence that one entity has on the health or well-being of another.
-
C.
healthIndicator
Indicates a measure or signal that reflects the health status or condition of an entity.
-
D.
diseaseType
Indicates that one entity is classified as a specific type or category of disease in relation to another entity.
-
E.
hasHealthConcern
chosen
Indicates that an entity has a specific health-related issue, condition, or concern associated with it.
- 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_69ab4ac14040819098b13f4a27d5c8ff |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd459ca6c81908505be96d097b739 |
completed | March 7, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69abd0d4e8648190b612eb09aa085451 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.