Triple
T37791282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British anti-Lewisite |
E942092
|
entity |
| Predicate | hasAntidoteRoleFor |
P194841
|
FINISHED |
| Object | arsenic compounds |
—
|
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: arsenic compounds | Statement: [British anti-Lewisite, hasAntidoteRoleFor, arsenic compounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAntidoteRoleFor Context triple: [British anti-Lewisite, hasAntidoteRoleFor, arsenic compounds]
-
A.
hasRoleInImmunity
Indicates that an entity functions in or contributes to an immune-related process or mechanism.
-
B.
hasVictimSupportRole
Indicates that an entity holds a role or responsibility related to providing support or assistance to a victim.
-
C.
hasRitualRoleIn
Indicates that an entity serves a specific ritual function or role within a particular ritual, ceremony, or sacred practice.
-
D.
hasVictimRoleWith
Indicates a relationship in which one entity occupies or is assigned the role of victim in relation to another entity or event.
-
E.
hasAntivenom
Indicates that an entity possesses or provides an antivenom specifically effective against another entity’s venom.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
| PDg | Predicate description generation | batch_69fd884b9d908190833de9500ff6d62a |
completed | May 8, 2026, 6:52 a.m. |
Created at: May 3, 2026, 4:19 p.m.