Triple
T38508941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common cuckoo |
E921846
|
entity |
| Predicate | vocalizationSex |
P29850
|
FINISHED |
| Object | male gives characteristic cuckoo call |
—
|
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: male gives characteristic cuckoo call | Statement: [Common cuckoo, vocalizationSex, male gives characteristic cuckoo call]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalizationSex Context triple: [Common cuckoo, vocalizationSex, male gives characteristic cuckoo call]
-
A.
vocalGender
Indicates the perceived or assigned gender associated with an entity’s voice in a vocal performance or recording.
-
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.
vocalizationMethod
Indicates the manner or technique by which an entity produces a sound or vocal expression.
-
E.
vocalGenderCombination
Indicates the combination of vocal genders (e.g., male, female, mixed) involved in a given vocal performance or vocal relationship.
- 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_69f76ea3c5448190aa7002fc1ba3f874 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.