Triple
T8913924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piranga olivacea |
E212249
|
entity |
| Predicate | callNote |
P29529
|
FINISHED |
| Object | sharp chip-burr 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: sharp chip-burr call | Statement: [Piranga olivacea, callNote, sharp chip-burr call]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callNote Context triple: [Piranga olivacea, callNote, sharp chip-burr 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.
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.
coordinateNote
Indicates that one note is coordinated with another, typically aligning or synchronizing their positions or roles within a shared structure or context.
-
D.
nowCalled
Indicates that an entity previously known by one name is currently referred to by a different name.
-
E.
protocolNote
Indicates that there is an associated note or annotation providing additional information or commentary about a protocol.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc65276b788190ab76372d0d871fef |
completed | April 1, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.