Triple
T27757799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mniotilta |
E701378
|
entity |
| Predicate | typicalVocalizationType |
P29850
|
FINISHED |
| Object | songbird 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: songbird vocalizations | Statement: [Mniotilta, typicalVocalizationType, songbird vocalizations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVocalizationType Context triple: [Mniotilta, typicalVocalizationType, songbird vocalizations]
-
A.
vocalizationMethod
Indicates the manner or technique by which an entity produces a sound or vocal expression.
-
B.
vocalizationCharacteristic
chosen
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
-
C.
vocalization
Indicates the act or manner of producing sounds or calls, typically as a means of communication.
-
D.
voiceType
Indicates the specific vocal style, quality, or role associated with an entity’s voice in a given context.
-
E.
vocalConfiguration
Indicates how an entity’s vocal or sound-producing characteristics are arranged or specified in relation to another entity or context.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_6a000a1d8fa88190a1d82ac746565c48 |
completed | May 10, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_6a0008b26eb88190ae03b2309a614774 |
completed | May 10, 2026, 4:25 a.m. |
Created at: April 27, 2026, 4:24 p.m.