Triple
T19040240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GPA |
E465980
|
entity |
| Predicate | hasPathologicalProcess |
P22707
|
FINISHED |
| Object | necrotizing vasculitis |
—
|
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: necrotizing vasculitis | Statement: [GPA, hasPathologicalProcess, necrotizing vasculitis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPathologicalProcess Context triple: [GPA, hasPathologicalProcess, necrotizing vasculitis]
-
A.
hasAssociatedDisease
Indicates that an entity is linked to, or commonly occurs with, a particular disease or medical condition.
-
B.
hasDiagnosticFinding
Indicates that a subject (e.g., a patient, test, or examination) is associated with a specific diagnostic observation, result, or abnormality identified during medical evaluation.
-
C.
hasEtiology
Indicates that one entity is the cause, origin, or underlying reason for the occurrence or existence of another entity or condition.
-
D.
pathologyFeature
chosen
Indicates that one entity is a pathological characteristic, sign, or abnormal finding associated with another entity in a medical or biological context.
-
E.
showsHealedPathologies
Indicates that an entity displays or reveals medical pathologies that have been healed or resolved.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d80054c88190a9d3a49aed504235 |
completed | April 20, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69e4a3001e388190aa6057266514e75a |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.