Triple
T1528190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European starling |
E32382
|
entity |
| Predicate | vocalizationCharacteristic |
P29850
|
FINISHED |
| Object | complex vocal mimicry |
—
|
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: complex vocal mimicry | Statement: [European starling, vocalizationCharacteristic, complex vocal mimicry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalizationCharacteristic Context triple: [European starling, vocalizationCharacteristic, complex vocal mimicry]
-
A.
vocalizationMethod
Indicates the manner or technique by which an entity produces a sound or vocal expression.
-
B.
vocalization
Indicates the act or manner of producing sounds or calls, typically as a means of communication.
-
C.
voiceType
Indicates the specific vocal style, quality, or role associated with an entity’s voice in a given context.
-
D.
hasVowelSystem
Indicates that an entity possesses a particular system or pattern of vowel sounds (a structured set of vowel phonemes or contrasts).
-
E.
hasVowelFeature
Indicates that an entity possesses a specific vowel-related phonological or articulatory feature.
- F. None of above. chosen
Provenance (4 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a933ddc5a881909cdf503f2bc29bd4 |
completed | March 5, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69a907ae8f688190ad9000ea1e018585 |
completed | March 5, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_69a933dce3488190b20f0e3d37d16371 |
completed | March 5, 2026, 7:42 a.m. |
Created at: March 4, 2026, 7:26 p.m.