Triple
T279763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asperger syndrome |
E5326
|
entity |
| Predicate | diagnosedBy |
P1340
|
FINISHED |
| Object | clinical assessment |
—
|
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: clinical assessment | Statement: [Asperger syndrome, diagnosedBy, clinical assessment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diagnosedBy Context triple: [Asperger syndrome, diagnosedBy, clinical assessment]
-
A.
diagnosedWith
Indicates that a subject has been identified, typically by a medical professional, as having a particular disease or medical condition.
-
B.
assessedBy
chosen
Indicates that an entity has been evaluated, examined, or judged by another entity (typically an agent or authority).
-
C.
diseaseType
Indicates that one entity is classified as a specific type or category of disease in relation to another entity.
-
D.
presentedTo
Indicates that something (such as an item, work, or information) was formally given, shown, or introduced by one party to another as the recipient.
-
E.
concludedBy
Indicates that an event, process, or state is brought to an end or finalized 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_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.