Triple
T18143367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colaptes auratus |
E434317
|
entity |
| Predicate | call |
P29529
|
FINISHED |
| Object | loud repeated wik-wik-wik 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: loud repeated wik-wik-wik call | Statement: [Colaptes auratus, call, loud repeated wik-wik-wik call]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: call Context triple: [Colaptes auratus, call, loud repeated wik-wik-wik call]
-
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.
callsTo
Indicates that one entity initiates a call or communication action directed toward another entity.
-
C.
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.
-
D.
callNumberSystem
Indicates a relationship where an entity uses or is organized according to a particular call number system for classification or identification.
-
E.
castBell
Indicates that an entity creates or forms a bell by pouring molten material into a mold or otherwise shaping it.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de0da3e081908732ed022f5eb90a |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.