Triple

T28495632
Position Surface form Disambiguated ID Type / Status
Subject Tachyglossidae E721099 entity
Predicate hasElectroreception P81228 FINISHED
Object present in snout 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: present in snout | Statement: [Tachyglossidae, hasElectroreception, present in snout]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasElectroreception
Context triple: [Tachyglossidae, hasElectroreception, present in snout]
  • A. usesElectroreceptionFor
    Indicates that an entity detects and interprets electrical fields in its environment specifically for the associated purpose or activity.
  • B. usesEcholocation
    Indicates that an entity employs echolocation, using reflected sound waves to detect, locate, or navigate around objects or other entities.
  • C. hasSensoryOrgans
    Indicates that an entity possesses organs specialized for sensing or perceiving stimuli from its environment.
  • D. hasSensation
    Indicates that an entity experiences or is subject to a particular sensory or perceptual feeling.
  • E. 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.
  • 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_69f01a5afdac8190ac6e72d5c100bd58 completed April 28, 2026, 2:24 a.m.
NER Named-entity recognition batch_69f6a28c7c148190bfc980aad9f678ca completed May 3, 2026, 1:19 a.m.
PD Predicate disambiguation batch_69f69fe1e3c88190830bb2e9f407357e completed May 3, 2026, 1:07 a.m.
Created at: April 28, 2026, 3:03 a.m.