Triple
T17940200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian muntjac |
E448564
|
entity |
| Predicate | alarmCall |
P31706
|
FINISHED |
| Object | loud bark-like 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 bark-like call | Statement: [Indian muntjac, alarmCall, loud bark-like call]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alarmCall Context triple: [Indian muntjac, alarmCall, loud bark-like call]
-
A.
alarmSignal
chosen
Indicates that an alarm or warning signal is being emitted, triggered, or active in response to some condition or event.
-
B.
alertSystem
Indicates that a system is configured to detect conditions and generate alerts or notifications in response.
-
C.
hasEmergencyAlarm
Indicates that an entity is equipped with or associated with an emergency alarm system that can be activated in urgent situations.
-
D.
alertMethod
Indicates the method or channel through which an alert or notification is delivered from a source to a recipient.
-
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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad9533688190bff773c183ed8505 |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.