Triple
T22629758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2,4-D |
E558515
|
entity |
| Predicate | usedFormulationType |
P10365
|
FINISHED |
| Object | ester formulations |
—
|
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: ester formulations | Statement: [2,4-D, usedFormulationType, ester formulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedFormulationType Context triple: [2,4-D, usedFormulationType, ester formulations]
-
A.
isFormulatedUsing
Indicates that something is created, defined, or expressed by means of a specified method, material, or set of components.
-
B.
exampleFormulation
Indicates that one entity serves as a representative or illustrative formulation or expression of another entity.
-
C.
hasFormulationType
chosen
Indicates the specific way something is physically prepared or presented, such as its dosage form, composition, or delivery format.
-
D.
hasFormulation
Indicates that one entity is expressed, prepared, or configured in a particular form or composition defined by another entity.
-
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_69e245467d9881908d6985bd0db7a1f1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e3febd081909ff21abef1e4035d |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3:02 p.m.