Triple

T8902258
Position Surface form Disambiguated ID Type / Status
Subject auditory cortex E211956 entity
Predicate hasFunctionalPart P35 FINISHED
Object core region 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: core region | Statement: [auditory cortex, hasFunctionalPart, core region]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFunctionalPart
Context triple: [auditory cortex, hasFunctionalPart, core region]
  • A. hasPart chosen
    Indicates that one entity is a component, segment, or constituent part of another entity.
  • B. hasPartIn
    Indicates that an entity participates in or plays a role within a larger event, process, or composite entity.
  • C. hasCommercialFunction
    Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
  • D. hasPartUsed
    Indicates that an entity utilizes another entity as a component or constituent part in its structure, function, or operation.
  • E. hasFunctionalGroup
    Indicates that one chemical entity contains or is characterized by a specific functional group as part of its molecular structure.
  • 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_69ca83918d3081909b326fa3750cb8c8 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc642a104081908df2d64e8f9ad0c8 completed April 1, 2026, 12:17 a.m.
PD Predicate disambiguation batch_69cc5ecf55248190a29f00fbf99f13c4 completed March 31, 2026, 11:54 p.m.
Created at: March 30, 2026, 6:55 p.m.