Triple
T30086543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | supramarginal gyrus |
E764616
|
entity |
| Predicate | BrodmannAreaOverlap |
P168424
|
FINISHED |
| Object | Brodmann area 40 |
—
|
NE NERFINISHED |
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: Brodmann area 40 | Statement: [supramarginal gyrus, BrodmannAreaOverlap, Brodmann area 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BrodmannAreaOverlap Context triple: [supramarginal gyrus, BrodmannAreaOverlap, Brodmann area 40]
-
A.
BrodmannAreaNumber
Indicates the specific Brodmann area identifier assigned to a region of the cerebral cortex based on its cytoarchitectonic characteristics.
-
B.
hasAssociatedBrainRegions
Indicates that certain brain regions are functionally, structurally, or conceptually linked to a given entity or process.
-
C.
cytoarchitectonicType
Indicates the specific cellular and structural organization pattern that characterizes a brain region’s tissue architecture.
-
D.
geographicOverlap
Indicates that two geographic areas share at least part of the same physical space or territory.
-
E.
damagedBrainRegion
Indicates that a particular brain region has been harmed, impaired, or structurally damaged.
- F. None of above. chosen
Provenance (4 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d6d35588190bf7b5ea2889ad6b8 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:04 p.m.