Triple
T35122304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asian openbill |
E1014193
|
entity |
| Predicate | typicalCall |
—
|
GENERATED |
| Object | mainly silent outside breeding colonies |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCall Context triple: [Asian openbill, typicalCall, mainly silent outside breeding colonies]
-
A.
exampleCall
Indicates that one entity initiates or performs a sample or illustrative call (such as a function, method, or communication) to another entity.
-
B.
typicalCaller
Indicates that one entity is the usual or most common initiator of calls or invocations to another entity.
-
C.
callType
chosen
Indicates the category or nature of a call (such as its purpose, direction, or handling), distinguishing one kind of call from another.
-
D.
typicalFunction
Indicates that something serves as the usual or characteristic function or role of an entity.
-
E.
typicalCallPrefix
Indicates the usual or standard prefix used when invoking or calling a particular entity (such as a function, method, or service).
- F. None of above.
Provenance (1 batch)
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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.