Triple
T26902859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conepatus |
E678076
|
entity |
| Predicate | defensiveBehavior |
P13663
|
FINISHED |
| Object | spraying foul-smelling liquid |
—
|
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: spraying foul-smelling liquid | Statement: [Conepatus, defensiveBehavior, spraying foul-smelling liquid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defensiveBehavior Context triple: [Conepatus, defensiveBehavior, spraying foul-smelling liquid]
-
A.
defensiveUse
Indicates that an entity uses something primarily for protection or defense against threats or attacks.
-
B.
defensiveTactics
chosen
Indicates the use or implementation of strategies, maneuvers, or methods intended to protect, guard, or defend against threats or attacks.
-
C.
defensiveConcern
Indicates a relationship where one entity is worried about protecting itself or another from potential harm, threat, or criticism.
-
D.
defendsHerselfBy
Indicates that a female entity protects or justifies herself using a specified method, action, or means.
-
E.
defensiveSide
Indicates which entity is acting in a defensive role or position relative to another entity or situation.
- 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_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 5:51 a.m.