Triple
T22693241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TDP-43 proteinopathy |
E561103
|
entity |
| Predicate | affectsBrainRegion |
P32708
|
FINISHED |
| Object | frontal cortex |
—
|
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: frontal cortex | Statement: [TDP-43 proteinopathy, affectsBrainRegion, frontal cortex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectsBrainRegion Context triple: [TDP-43 proteinopathy, affectsBrainRegion, frontal cortex]
-
A.
hasAssociatedBrainRegions
chosen
Indicates that certain brain regions are functionally, structurally, or conceptually linked to a given entity or process.
-
B.
BrodmannAreaNumber
Indicates the specific Brodmann area identifier assigned to a region of the cerebral cortex based on its cytoarchitectonic characteristics.
-
C.
brain
Indicates that an entity functions as the brain (central cognitive or control organ) of another entity.
-
D.
brainSectionedAt
Indicates that a brain has been divided or cut at a specified anatomical location or plane.
-
E.
hemisphereDominance
Indicates which brain hemisphere (left or right) is functionally dominant for a given cognitive or neural process in an 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789c6ae481908975b7d27e7624ac |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.