Triple
T479444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | southern right whale |
E9133
|
entity |
| Predicate | acousticCommunication |
P1338
|
FINISHED |
| Object | low-frequency 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: low-frequency vocalizations | Statement: [southern right whale, acousticCommunication, low-frequency vocalizations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acousticCommunication Context triple: [southern right whale, acousticCommunication, low-frequency vocalizations]
-
A.
acousticProperty
Indicates the relationship between an entity and its sound-related characteristics, such as loudness, pitch, timbre, or other acoustic features.
-
B.
vocalization
chosen
Indicates the act or manner of producing sounds or calls, typically as a means of communication.
-
C.
vocalizationMethod
Indicates the manner or technique by which an entity produces a sound or vocal expression.
-
D.
soundReproductionMethod
Indicates the method or technique used to reproduce or play back sound.
-
E.
soundCharacter
Indicates a relationship where one entity specifies the quality, style, or distinguishing characteristics of a sound produced or perceived in another entity.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f056459881909749764cc4a7f9e8 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf1d5848190a7da27e2fddc136f |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.