Triple
T36599749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | microscopic polyangiitis |
E902884
|
entity |
| Predicate | bodySystemAffected |
P63668
|
FINISHED |
| Object | kidneys |
—
|
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: kidneys | Statement: [microscopic polyangiitis, bodySystemAffected, kidneys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodySystemAffected Context triple: [microscopic polyangiitis, bodySystemAffected, kidneys]
-
A.
affectsBody
Indicates that one entity produces a physical impact, change, or influence on the body of another entity.
-
B.
affectsAnatomicalLocation
chosen
Indicates that one entity produces an effect on, or has an impact at, a specific anatomical location.
-
C.
hasBodyRegion
Indicates that an entity possesses, includes, or is associated with a specific anatomical or bodily region.
-
D.
bodyOrganization
Indicates how the parts or components of a body are arranged, structured, or organized in relation to each other.
-
E.
typicalBodyPart
Indicates that one entity is a body part that is characteristically or normally associated with 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:11 p.m.