Triple
T30178957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brodmann area 42 |
E767145
|
entity |
| Predicate | BrodmannMapPublicationYear |
P78646
|
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 42, BrodmannMapPublicationYear, 1909]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BrodmannMapPublicationYear Context triple: [Brodmann area 42, BrodmannMapPublicationYear, 1909]
-
A.
introducedInPublicationYear
chosen
Indicates the year in which something (such as a concept, method, or product) was first introduced or presented in a publication.
-
B.
collectedInPublicationYear
Indicates that the collecting event or data record was documented in a publication that appeared in the specified year.
-
C.
appearsInPublicationYear
Indicates that an entity is featured in a publication that was released in a specific year.
-
D.
frontiersReferenceYear
Indicates the specific year to which a given Frontiers reference or citation pertains.
-
E.
firstStandardPublicationYear
Indicates the year in which an entity’s work was first formally published according to a recognized standard or official publication record.
- 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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 7:26 p.m.