Triple
T38508958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common cuckoo |
E921846
|
entity |
| Predicate | onomatopoeicNameRefersTo |
P190972
|
FINISHED |
| Object | male’s cuck-oo 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’s cuck-oo call | Statement: [Common cuckoo, onomatopoeicNameRefersTo, male’s cuck-oo call]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onomatopoeicNameRefersTo Context triple: [Common cuckoo, onomatopoeicNameRefersTo, male’s cuck-oo call]
-
A.
onomatopoeicNameIn
chosen
Indicates that one entity serves as an onomatopoeic name or sound-based designation for another entity within a given context or language.
-
B.
nameLiterallyMeans
Indicates that the literal meaning or direct translation of one entity’s name is given by the other entity.
-
C.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
-
D.
namedForPortmanteauOf
Indicates that something is named using a portmanteau formed by blending parts of two or more other names or words.
-
E.
colloquialNameOf
Indicates that one entity is an informal, colloquial, or commonly used name referring to 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_69f76ea3c5448190aa7002fc1ba3f874 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.