Triple
T27348134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | arcuate fasciculus |
E684282
|
entity |
| Predicate | abnormalityAssociatedWith |
P76100
|
FINISHED |
| Object | dyslexia |
—
|
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: dyslexia | Statement: [arcuate fasciculus, abnormalityAssociatedWith, dyslexia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abnormalityAssociatedWith Context triple: [arcuate fasciculus, abnormalityAssociatedWith, dyslexia]
-
A.
dysfunctionAssociatedWith
Indicates a relationship where a dysfunction is linked or correlated with another condition, factor, or entity.
-
B.
deficiencyAssociatedWith
Indicates an association where a lack or insufficiency of one entity is related to the occurrence, presence, or severity of another entity.
-
C.
hasEponymousDisease
Indicates that an entity (typically a person) has a disease named after them.
-
D.
hasAssociatedDisease
chosen
Indicates that an entity is linked to, or commonly occurs with, a particular disease or medical condition.
-
E.
associatedDiseaseAgentType
Indicates the type or category of disease-causing agent that is associated with a given disease or condition.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62ba5a110819092fe773ade8fec2e |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 11:46 a.m.