Triple
T33249208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | go-away-birds |
E851188
|
entity |
| Predicate | communicationFunctionOfCall |
P29529
|
FINISHED |
| Object | alarm 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: alarm call | Statement: [go-away-birds, communicationFunctionOfCall, alarm call]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationFunctionOfCall Context triple: [go-away-birds, communicationFunctionOfCall, alarm call]
-
A.
communicationFunction
Indicates that one entity serves a communicative role or purpose in relation to another, such as conveying, mediating, or facilitating the exchange of information.
-
B.
communicationService
Indicates a relationship where one entity provides or facilitates a means for another entity to exchange information or messages.
-
C.
callsTo
Indicates that one entity initiates a call or communication action directed toward another entity.
-
D.
communicationRelayCapability
Indicates that an entity has the ability to relay or forward communications between other entities or systems.
-
E.
callType
chosen
Indicates the category or nature of a call (such as its purpose, direction, or handling), distinguishing one kind of call from another.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:31 a.m.