Triple
T26902817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mephitis |
E678075
|
entity |
| Predicate | usesSprayFor |
P13821
|
FINISHED |
| Object | predator deterrence |
—
|
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: predator deterrence | Statement: [Mephitis, usesSprayFor, predator deterrence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSprayFor Context triple: [Mephitis, usesSprayFor, predator deterrence]
-
A.
hasSpray
Indicates that one entity possesses, contains, or is equipped with a spray or spraying capability in relation to another entity or context.
-
B.
producesAerosol
Indicates that one entity generates or emits an aerosol (a suspension of fine solid particles or liquid droplets in air) as a result of its action or process.
-
C.
usedAgainst
chosen
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
-
D.
organUsed
Indicates that a particular organ is utilized in performing an action or function.
-
E.
fireUse
Indicates the use or application of fire by one entity on, with, or for another entity or object.
- 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_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 5:51 a.m.