Triple
T37791281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British anti-Lewisite |
E942092
|
entity |
| Predicate | isFormulatedWith |
P30732
|
FINISHED |
| Object | peanut oil |
—
|
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: peanut oil | Statement: [British anti-Lewisite, isFormulatedWith, peanut oil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFormulatedWith Context triple: [British anti-Lewisite, isFormulatedWith, peanut oil]
-
A.
coFormulatedWith
chosen
Indicates that one entity is formulated together with another as part of the same combined product or composition.
-
B.
isFormulatedUsing
Indicates that something is created, defined, or expressed by means of a specified method, material, or set of components.
-
C.
isFormulatedBy
Indicates that something (such as a plan, idea, or substance) is created, devised, or composed by a particular agent or source.
-
D.
formulatedIn
Indicates that something was created, developed, or expressed within a particular context, place, or framework.
-
E.
coFormulated
Indicates that two or more entities were jointly formulated, designed, or created together as part of the same process or product.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.