Triple
T22629765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2,4-D |
E558515
|
entity |
| Predicate | hasTargetSiteOfAction |
P148987
|
FINISHED |
| Object | auxin receptors in plants |
—
|
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: auxin receptors in plants | Statement: [2,4-D, hasTargetSiteOfAction, auxin receptors in plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTargetSiteOfAction Context triple: [2,4-D, hasTargetSiteOfAction, auxin receptors in plants]
-
A.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
B.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
-
C.
canTarget
Indicates that one entity is able or permitted to select, aim at, or direct its action or effect toward another entity as a target.
-
D.
hasObservationTarget
Indicates that an observation is directed toward or focused on a particular target entity.
-
E.
isTargetIn
Indicates that a specified entity lies within, or is contained inside, a given target region, set, or scope.
- 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_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. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:02 p.m.