Triple
T19838193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caspian tern |
E476652
|
entity |
| Predicate | vocalizationDescription |
P29850
|
FINISHED |
| Object | loud harsh croaking calls |
—
|
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: loud harsh croaking calls | Statement: [Caspian tern, vocalizationDescription, loud harsh croaking calls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalizationDescription Context triple: [Caspian tern, vocalizationDescription, loud harsh croaking calls]
-
A.
vocalization
Indicates the act or manner of producing sounds or calls, typically as a means of communication.
-
B.
vocalizationCharacteristic
chosen
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
-
C.
vocalizationMethod
Indicates the manner or technique by which an entity produces a sound or vocal expression.
-
D.
vocalizationUsage
Indicates how a particular vocalization is used or applied within a communicative or behavioral 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65803bb988190a4e7c0035058feba |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.