Triple
T30154511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brodmann area 41 |
E766486
|
entity |
| Predicate | BrodmannMapYearDescribed |
P1353
|
FINISHED |
| Object | 1909 |
—
|
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: 1909 | Statement: [Brodmann area 41, BrodmannMapYearDescribed, 1909]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BrodmannMapYearDescribed Context triple: [Brodmann area 41, BrodmannMapYearDescribed, 1909]
-
A.
introducedInPublicationYear
Indicates the year in which something (such as a concept, method, or product) was first introduced or presented in a publication.
-
B.
yearDescribed
chosen
Indicates the year in which something (typically a species, object, or concept) was formally described or documented.
-
C.
yearDescribedAs
Indicates the specific year in which something was formally characterized, documented, or described.
-
D.
recognizedByIAUYear
Indicates the year in which an astronomical object or feature was officially recognized or approved by the International Astronomical Union (IAU).
-
E.
yearOfStandardization
Indicates the specific year in which something was formally standardized or officially adopted as a standard.
- 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_69f67ed66ab48190928ceb36710c1ed2 |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:20 p.m.