Triple
T35757124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paget–Schroetter syndrome |
E1033471
|
entity |
| Predicate | hasRiskGroup |
P18422
|
FINISHED |
| Object | young individuals |
—
|
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: young individuals | Statement: [Paget–Schroetter syndrome, hasRiskGroup, young individuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiskGroup Context triple: [Paget–Schroetter syndrome, hasRiskGroup, young individuals]
-
A.
hasRiskFrom
Indicates that one entity is exposed to or may suffer potential harm, loss, or adverse effects as a result of another entity.
-
B.
hasRiskStatus
Indicates the level or category of risk currently associated with an entity.
-
C.
hasRiskFactorFor
Indicates that one entity contributes to or increases the likelihood of another entity experiencing a particular risk or adverse outcome.
-
D.
hasCountryOfRisk
Indicates that an entity is associated with a country where it faces significant exposure, vulnerability, or potential risk.
-
E.
riskGroup
chosen
Indicates that an entity belongs to a category of individuals or items that share an elevated level of risk relative to others.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 3, 2026, 4:06 p.m.