Triple
T19040316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PR3-ANCA |
E465982
|
entity |
| Predicate | laboratoryTestType |
P133661
|
FINISHED |
| Object | autoantibody test |
—
|
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: autoantibody test | Statement: [PR3-ANCA, laboratoryTestType, autoantibody test]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laboratoryTestType Context triple: [PR3-ANCA, laboratoryTestType, autoantibody test]
-
A.
laboratoryAnalysis
Indicates that a sample or material is being examined, tested, or measured using scientific procedures in a laboratory setting.
-
B.
affectsLaboratoryTest
Indicates that one entity has an influence on, alters, or changes the outcome, value, or interpretation of a laboratory test.
-
C.
hasKeyLaboratory
Indicates that an entity possesses or is associated with a designated key laboratory, typically as an important research or development facility under its responsibility.
-
D.
hasLaboratoryServices
Indicates that one entity provides or makes available laboratory services to another entity or within a given context.
-
E.
hasLaboratorySystem
Indicates that one entity possesses, uses, or is associated with a particular laboratory system.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e4ad8f6f7c8190af645bf08823ee2b |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:02 p.m.