Triple

T36281520
Position Surface form Disambiguated ID Type / Status
Subject Ptereleotridae E892953 entity
Predicate riskResponse P185091 FINISHED
Object darting into burrows or crevices when threatened 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: darting into burrows or crevices when threatened | Statement: [Ptereleotridae, riskResponse, darting into burrows or crevices when threatened]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: riskResponse
Context triple: [Ptereleotridae, riskResponse, darting into burrows or crevices when threatened]
  • A. riskType
    Indicates the category or nature of risk associated with an entity, event, or relationship.
  • B. riskElement
    Indicates that one entity is a risk-related component, factor, or contributor associated with another entity within a risk context.
  • C. risk
    Indicates that one entity is exposed or subject to potential harm, loss, or adverse outcome arising from another entity, action, or situation.
  • D. riskTaken
    Indicates that an entity has undertaken an action or decision involving exposure to potential loss, harm, or uncertainty.
  • E. riskBasis
    Indicates the underlying factor, condition, or rationale that forms the basis for assessing or assigning risk in a given context.
  • 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_69f76e4955c08190b8cfddca34fc0242 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7bb1d6b70819091227bd011734d19 completed May 3, 2026, 9:16 p.m.
PD Predicate disambiguation batch_69f7b9a4aad48190a62e41c5e39339d9 completed May 3, 2026, 9:09 p.m.
PDg Predicate description generation batch_69f7ba6c27e081908868a2b50d1d603c completed May 3, 2026, 9:13 p.m.
Created at: May 3, 2026, 4:09 p.m.