Triple
T26902790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mephitis |
E678075
|
entity |
| Predicate | defensiveMechanism |
P119087
|
FINISHED |
| Object | noxious anal gland spray |
—
|
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: noxious anal gland spray | Statement: [Mephitis, defensiveMechanism, noxious anal gland spray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defensiveMechanism Context triple: [Mephitis, defensiveMechanism, noxious anal gland spray]
-
A.
copingMechanism
Indicates a way in which an entity responds to, manages, or adapts to stress, difficulty, or emotional challenges.
-
B.
defendsHerselfBy
Indicates that a female entity protects or justifies herself using a specified method, action, or means.
-
C.
escapeMechanism
Indicates a means or method by which an entity avoids, evades, or breaks free from a threat, constraint, or controlling influence.
-
D.
defensiveUse
chosen
Indicates that an entity uses something primarily for protection or defense against threats or attacks.
-
E.
usesHumorAsDefense
Indicates that an entity habitually employs humor or joking behavior to cope with, deflect, or protect themselves from emotional discomfort, stress, or vulnerability.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 5:51 a.m.