Triple
T21853951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | entorhinal cortex |
E539573
|
entity |
| Predicate | cytoarchitectonicType |
P145935
|
FINISHED |
| Object | allocortex |
—
|
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: allocortex | Statement: [entorhinal cortex, cytoarchitectonicType, allocortex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cytoarchitectonicType Context triple: [entorhinal cortex, cytoarchitectonicType, allocortex]
-
A.
BrodmannAreaNumber
Indicates the specific Brodmann area identifier assigned to a region of the cerebral cortex based on its cytoarchitectonic characteristics.
-
B.
anatomicalType
Indicates that one entity is classified as a specific anatomical category or kind of anatomical structure in relation to another.
-
C.
hemisphereDominance
Indicates which brain hemisphere (left or right) is functionally dominant for a given cognitive or neural process in an entity.
-
D.
cranialStructureFunction
Indicates that a relationship exists between a cranial structure and the specific function or role it performs.
-
E.
nucleusType
Indicates the specific kind or classification of nucleus associated with an entity.
- 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_69e0c47829648190bbe2d1d7033768ec |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0bd5ba9288190af962117124f6483 |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:56 p.m.