Triple

T8519734
Position Surface form Disambiguated ID Type / Status
Subject Norway rat E201664 entity
Predicate sensoryCommunication P83093 FINISHED
Object ultrasonic vocalizations 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: ultrasonic vocalizations | Statement: [Norway rat, sensoryCommunication, ultrasonic vocalizations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sensoryCommunication
Context triple: [Norway rat, sensoryCommunication, ultrasonic vocalizations]
  • A. sensorySystem
    Indicates that one entity functions as the sensory system (or part of it) of another, enabling the detection and processing of internal or external stimuli.
  • B. senses
    Indicates that an entity perceives or detects another entity or stimulus through one of its senses.
  • C. providesSensoryEffects
    Indicates that one entity causes or contributes to sensory experiences or perceptions in another entity.
  • D. hasSensoryAdaptation
    Indicates that an entity possesses a specialized sensory modification or adjustment that enhances its ability to detect, process, or respond to environmental stimuli.
  • E. hasSensoryOrgans
    Indicates that an entity possesses organs specialized for sensing or perceiving stimuli from its environment.
  • F. None of above. chosen

Provenance (4 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_69ca8321bb44819081b74df0b710276d completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe627de908190b463da0f26da4ffb completed March 31, 2026, 3:20 p.m.
PD Predicate disambiguation batch_69cbd10f64b4819080859057c19e58f0 completed March 31, 2026, 1:50 p.m.
PDg Predicate description generation batch_69cbe30d453481908f897ed2b06e7534 completed March 31, 2026, 3:06 p.m.
Created at: March 30, 2026, 6:16 p.m.