Triple
T22629734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2,4-D |
E558515
|
entity |
| Predicate | relativelySpares |
P33796
|
FINISHED |
| Object | grasses |
—
|
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: grasses | Statement: [2,4-D, relativelySpares, grasses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativelySpares Context triple: [2,4-D, relativelySpares, grasses]
-
A.
spares
Indicates that one entity chooses not to harm, punish, or destroy another entity when it has the power or opportunity to do so.
-
B.
typicallySpared
chosen
Indicates that an entity is usually not affected by, excluded from, or left untouched by a particular action, process, or condition.
-
C.
laterSparedBy
Indicates that an entity was initially at risk but was subsequently spared or saved by another entity at a later time.
-
D.
replacedPartOf
Indicates that one entity has taken the place of another entity as a component or part within a larger whole.
-
E.
isRelatively
Indicates that one entity is being described, measured, or evaluated in relation to another entity or reference point, rather than in absolute terms.
- 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.