Triple
T22629762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2,4-D |
E558515
|
entity |
| Predicate | hasSoilHalfLife |
P38026
|
FINISHED |
| Object | on the order of days to weeks |
—
|
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: on the order of days to weeks | Statement: [2,4-D, hasSoilHalfLife, on the order of days to weeks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSoilHalfLife Context triple: [2,4-D, hasSoilHalfLife, on the order of days to weeks]
-
A.
hasSoil
Indicates that one entity possesses, contains, or is associated with a particular type or instance of soil.
-
B.
hasEliminationHalfLife
chosen
Indicates the duration required for half of a substance or entity to be removed, degraded, or rendered inactive within a given system or context.
-
C.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
-
D.
hasSoilProperty
Indicates that a soil entity possesses or is characterized by a specific soil-related property or attribute.
-
E.
mostStableIsotopeHalfLife
Indicates the duration of time it takes for half of the atoms in the most stable isotope of an element to decay.
- 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.