Triple
T13855357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple Grandin |
E333048
|
entity |
| Predicate | hasAutismSpectrumCondition |
P1005
|
FINISHED |
| Object | autism |
—
|
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 | Statement: [Temple Grandin, hasAutismSpectrumCondition, autism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAutismSpectrumCondition Context triple: [Temple Grandin, hasAutismSpectrumCondition, autism]
-
A.
diagnosedWith
chosen
Indicates that a subject has been identified, typically by a medical professional, as having a particular disease or medical condition.
-
B.
hasTypicalConditions
Indicates that something is associated with conditions or circumstances that are commonly or normally present for it.
-
C.
hasDyslexia
Indicates that an entity experiences dyslexia, a learning difficulty affecting reading, writing, or spelling abilities.
-
D.
hasSynaesthesia
Indicates that an entity experiences synaesthesia, where stimulation of one sensory or cognitive pathway involuntarily triggers perceptions in another.
-
E.
hasDisabilityRepresentation
Indicates that something includes, portrays, or accounts for the presence and experiences of people with disabilities.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02db9c9c81909bb2d2fbfb7394b1 |
completed | April 14, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:14 p.m.