Triple
T8467109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mus musculus |
E200190
|
entity |
| Predicate | hearingRange |
P64259
|
FINISHED |
| Object | ultrasonic communication |
—
|
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 communication | Statement: [Mus musculus, hearingRange, ultrasonic communication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hearingRange Context triple: [Mus musculus, hearingRange, ultrasonic communication]
-
A.
hearingType
Indicates the type or category of a hearing event or proceeding that takes place.
-
B.
soundFrequencyRange
chosen
Indicates the range of sound frequencies within which the related entity operates, is effective, or is characterized.
-
C.
canHear
Indicates that one entity is able to perceive sounds produced by another entity.
-
D.
mayHear
Indicates that one entity is permitted or able to hear sounds, speech, or audio produced by another entity.
-
E.
vocalRange
Indicates the span of pitches or notes that an entity (such as a singer or instrument) is capable of producing.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4d2eb648190b606411eb6a8f7ea |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.