Triple
T30086958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supplementary motor area |
E764625
|
entity |
| Predicate | hasBrodmannAreaNumber |
P86291
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [Supplementary motor area, hasBrodmannAreaNumber, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrodmannAreaNumber Context triple: [Supplementary motor area, hasBrodmannAreaNumber, 6]
-
A.
BrodmannAreaNumber
chosen
Indicates the specific Brodmann area identifier assigned to a region of the cerebral cortex based on its cytoarchitectonic characteristics.
-
B.
BrodmannAreaOverlap
Indicates that two brain regions share a common spatial extent within one or more Brodmann areas.
-
C.
BrodmannMapAuthor
Indicates that one entity is the author or originator of a specific Brodmann brain area map associated with the other entity.
-
D.
hasAssociatedBrainRegions
Indicates that certain brain regions are functionally, structurally, or conceptually linked to a given entity or process.
-
E.
cytoarchitectonicRegion
Indicates a relationship where a brain area is classified as belonging to a specific cytoarchitectonic region defined by its cellular structure and organization.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 29, 2026, 7:04 p.m.