Triple
T4919578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirk’s dik-dik |
E110429
|
entity |
| Predicate | antiPredatorBehavior |
P26653
|
FINISHED |
| Object | freezing and hiding in cover |
—
|
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: freezing and hiding in cover | Statement: [Kirk’s dik-dik, antiPredatorBehavior, freezing and hiding in cover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antiPredatorBehavior Context triple: [Kirk’s dik-dik, antiPredatorBehavior, freezing and hiding in cover]
-
A.
antiPredatorStrategy
chosen
Indicates a behavior or adaptation used to avoid, deter, or reduce the risk of predation by other organisms.
-
B.
usesForPreyCapture
Indicates that an entity employs another entity as a means or tool for capturing prey.
-
C.
preysOn
Indicates that one entity hunts, kills, and consumes another entity as a food source.
-
D.
predators
Indicates a relationship where one organism hunts, kills, and consumes another organism as a food source.
-
E.
preyCaptureMechanism
Indicates the method or strategy an organism uses to locate, seize, and secure its prey.
- 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6faa78b88190938bee2f81025083 |
completed | March 20, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.