Triple

T10639842
Position Surface form Disambiguated ID Type / Status
Subject Mormyridae E250691 entity
Predicate sensorySpecialization P81228 FINISHED
Object electroreception 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: electroreception | Statement: [Mormyridae, sensorySpecialization, electroreception]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sensorySpecialization
Context triple: [Mormyridae, sensorySpecialization, electroreception]
  • 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. hasSensoryAdaptation chosen
    Indicates that an entity possesses a specialized sensory modification or adjustment that enhances its ability to detect, process, or respond to environmental stimuli.
  • C. senses
    Indicates that an entity perceives or detects another entity or stimulus through one of its senses.
  • D. hasSensoryOrgans
    Indicates that an entity possesses organs specialized for sensing or perceiving stimuli from its environment.
  • E. sensoryCommunication
    Indicates a relationship where one entity conveys or exchanges information with another through sensory signals or perception-based means.
  • 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_69d6aa5a4c4881908f39be6efe5981e5 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6dfcbe5308190986bba438d19e852 completed April 8, 2026, 11:07 p.m.
PD Predicate disambiguation batch_69d6dd83b114819098e84dc658e82d7e completed April 8, 2026, 10:58 p.m.
Created at: April 8, 2026, 9:04 p.m.