Triple
T18213213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Prognostic Index |
E436083
|
entity |
| Predicate | riskGroupBasis |
P26874
|
FINISHED |
| Object | number of adverse prognostic factors |
—
|
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: number of adverse prognostic factors | Statement: [International Prognostic Index, riskGroupBasis, number of adverse prognostic factors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskGroupBasis Context triple: [International Prognostic Index, riskGroupBasis, number of adverse prognostic factors]
-
A.
riskGroup
Indicates that an entity belongs to a category of individuals or items that share an elevated level of risk relative to others.
-
B.
riskBasis
chosen
Indicates the underlying factor, condition, or rationale that forms the basis for assessing or assigning risk in a given context.
-
C.
riskBased
Indicates that something is determined, prioritized, or managed according to the level or assessment of risk involved.
-
D.
riskType
Indicates the category or nature of risk associated with an entity, event, or relationship.
-
E.
riskAssessmentBy
Indicates that a risk assessment is performed, evaluated, or provided by a specific agent or 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e22a26308190a6720b41a9bbfc2d |
completed | April 19, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.