Triple
T25665501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | black-bellied bustard |
E643501
|
entity |
| Predicate | displayCall |
P158967
|
FINISHED |
| Object | booming 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: booming call | Statement: [black-bellied bustard, displayCall, booming call]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displayCall Context triple: [black-bellied bustard, displayCall, booming call]
-
A.
callsTo
Indicates that one entity initiates a call or communication action directed toward another entity.
-
B.
hasCallInNumber
Indicates that an entity has an associated telephone number designated for receiving incoming calls.
-
C.
callType
Indicates the category or nature of a call (such as its purpose, direction, or handling), distinguishing one kind of call from another.
-
D.
nowCalled
Indicates that an entity previously known by one name is currently referred to by a different name.
-
E.
famousCall
Indicates that one entity makes a phone call to another entity who is widely known or celebrated.
- F. None of above. chosen
Provenance (4 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb2e5e548190a0b3a84b02c07940 |
completed | May 2, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 7:03 p.m.