Triple
T32883190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brodmann area 6 |
E841123
|
entity |
| Predicate | BrodmannNumber |
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: [Brodmann area 6, BrodmannNumber, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BrodmannNumber Context triple: [Brodmann area 6, BrodmannNumber, 6]
-
A.
BrodmannAreaNumber
chosen
Indicates the specific Brodmann area identifier assigned to a region of the cerebral cortex based on its cytoarchitectonic characteristics.
-
B.
cytoarchitectonicRegion
Indicates a relationship where a brain area is classified as belonging to a specific cytoarchitectonic region defined by its cellular structure and organization.
-
C.
BrodmannAreaOverlap
Indicates that two brain regions share a common spatial extent within one or more Brodmann areas.
-
D.
cytoarchitectonicType
Indicates the specific cellular and structural organization pattern that characterizes a brain region’s tissue architecture.
-
E.
hasAssociatedBrainRegions
Indicates that certain brain regions are functionally, structurally, or conceptually linked to a given entity or process.
- 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:18 a.m.