Triple
T4202063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonoran Desert toad |
E86088
|
entity |
| Predicate | secretes |
P54345
|
FINISHED |
| Object | bufotoxins |
—
|
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: bufotoxins | Statement: [Sonoran Desert toad, secretes, bufotoxins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secretes Context triple: [Sonoran Desert toad, secretes, bufotoxins]
-
A.
revealedSecretOf
Indicates that one entity has disclosed or exposed confidential or previously unknown information belonging to another entity.
-
B.
secretive
Indicates that an entity deliberately withholds information or conceals its thoughts, actions, or intentions from others.
-
C.
keepsSecretAbout
Indicates that one entity intentionally withholds or conceals information regarding another specified entity or topic from others.
-
D.
secondSecretTheme
Indicates that an entity has or is associated with a secondary, hidden or underlying thematic element beyond its primary theme.
-
E.
penaltyForRevealingSecrets
Indicates that an entity incurs a punishment or negative consequence as a result of disclosing confidential or secret information.
- 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af037f1de4819088d6bf544317a694 |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af01959c4881909eb1adcb3bdadbe6 |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af02e4e2308190b527e3b78eb8fa71 |
completed | March 9, 2026, 5:27 p.m. |
Created at: March 9, 2026, 3:49 p.m.