Triple
T28019199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | common loon |
E707638
|
entity |
| Predicate | callDescription |
P29529
|
FINISHED |
| Object | haunting yodel-like 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: haunting yodel-like calls | Statement: [common loon, callDescription, haunting yodel-like calls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callDescription Context triple: [common loon, callDescription, haunting yodel-like calls]
-
A.
callType
chosen
Indicates the category or nature of a call (such as its purpose, direction, or handling), distinguishing one kind of call from another.
-
B.
callingPoint
Indicates that one entity serves as a stop, station, or intermediate point that another entity (such as a route, journey, or service) calls at or passes through.
-
C.
callCharacteristic
Indicates a defining quality, feature, or attribute associated with a particular call or calling event.
-
D.
callsTo
Indicates that one entity initiates a call or communication action directed toward another entity.
-
E.
callingStyle
Indicates the manner or convention by which one entity initiates or performs a call or invocation on 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63c09382c81909819e586594cd93a |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:09 p.m.