Triple

T37823548
Position Surface form Disambiguated ID Type / Status
Subject Pacinian corpuscle E942989 entity
Predicate respondsBestTo P2278 FINISHED
Object vibration around 200 Hz 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: vibration around 200 Hz | Statement: [Pacinian corpuscle, respondsBestTo, vibration around 200 Hz]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: respondsBestTo
Context triple: [Pacinian corpuscle, respondsBestTo, vibration around 200 Hz]
  • A. respondsTo chosen
    Indicates that one entity replies or reacts to a message, action, or stimulus originating from another entity.
  • B. hasCommandResponsibilityFor
    Indicates that one entity holds authoritative control over, and is responsible for directing and overseeing, the actions or operations of another entity.
  • C. operatesInResponseTo
    Indicates that an action or process is carried out as a direct reaction to a specific trigger, event, or condition.
  • D. wasResponseTo
    Indicates that one event, action, or communication occurred as a direct reply or reaction to a preceding event, action, or communication.
  • E. holdsBestFor
    Indicates that one entity considers or maintains another entity as the most suitable or optimal choice for a particular purpose or context.
  • 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_69f76ee987588190906506e759be5db3 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbbae559a8819086ef839973f8d9b2 completed May 6, 2026, 10:04 p.m.
PD Predicate disambiguation batch_69fbb1440fa08190abf25ba684f75b6e completed May 6, 2026, 9:23 p.m.
Created at: May 3, 2026, 4:19 p.m.