Triple
T279768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asperger syndrome |
E5326
|
entity |
| Predicate | replacedByDiagnosis |
P101
|
FINISHED |
| Object | autism spectrum disorder (DSM-5) |
—
|
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: autism spectrum disorder (DSM-5) | Statement: [Asperger syndrome, replacedByDiagnosis, autism spectrum disorder (DSM-5)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedByDiagnosis Context triple: [Asperger syndrome, replacedByDiagnosis, autism spectrum disorder (DSM-5)]
-
A.
diagnosedWith
Indicates that a subject has been identified, typically by a medical professional, as having a particular disease or medical condition.
-
B.
wasSupersededBy
chosen
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
C.
replacedSystemUsedUntil
Indicates that one system was used up until it was replaced by another system.
-
D.
amendedBy
Indicates that one entity has been modified, revised, or updated as a result of changes made by another entity.
-
E.
rejectedOrModifiedBy
Indicates that a proposal, request, or item was either not accepted as-is or was altered by a particular agent or authority.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25def95c48190bb8ab2259f67b583 |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b765f488190b2cbe4b45cd42821 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.