Triple
T30154530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brodmann area 41 |
E766486
|
entity |
| Predicate | foundInGyrus |
P66393
|
FINISHED |
| Object | Heschl gyrus |
—
|
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: Heschl gyrus | Statement: [Brodmann area 41, foundInGyrus, Heschl gyrus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInGyrus Context triple: [Brodmann area 41, foundInGyrus, Heschl gyrus]
-
A.
foundInVolume
Indicates that one entity is physically or logically contained within, or occurs in, a specific volume (such as a book volume, data volume, or bounded collection).
-
B.
foundInStructure
chosen
Indicates that an entity is located within, contained by, or structurally part of another entity or structure.
-
C.
foundInRite
Indicates that something (such as an element, object, or action) occurs within, is used in, or is otherwise present as part of a specific rite or ritual.
-
D.
locatedInHeadTempleRegion
Indicates that something is situated within the geographic or administrative region associated with the head temple.
-
E.
BrodmannAreaNumber
Indicates the specific Brodmann area identifier assigned to a region of the cerebral cortex based on its cytoarchitectonic characteristics.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: April 29, 2026, 7:20 p.m.