Triple
T279774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asperger syndrome |
E5326
|
entity |
| Predicate | treatedWith |
P2367
|
FINISHED |
| Object | social skills training |
—
|
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: social skills training | Statement: [Asperger syndrome, treatedWith, social skills training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatedWith Context triple: [Asperger syndrome, treatedWith, social skills training]
-
A.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
B.
underwent
Indicates that an entity experienced or was subjected to a process, event, or change, typically as the patient of an action.
-
C.
considered
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
-
D.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
E.
usedOn
chosen
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to 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_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.