Triple
T38559809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhodococcus |
E928045
|
entity |
| Predicate | plantInteraction |
P3806
|
FINISHED |
| Object | includes plant pathogenic species |
—
|
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: includes plant pathogenic species | Statement: [Rhodococcus, plantInteraction, includes plant pathogenic species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plantInteraction Context triple: [Rhodococcus, plantInteraction, includes plant pathogenic species]
-
A.
plantActivity
Indicates an action, process, or behavior being carried out by a plant or involving plant-related functions.
-
B.
involvesPlant
chosen
Indicates that the relationship or action includes or pertains to a plant as a participating entity.
-
C.
plantCollection
Indicates that one entity maintains or possesses a collection of plants, typically grouped or curated as a set.
-
D.
plantBecame
Indicates that an entity transitioned into or developed into a plant, changing its state or classification to that of a plant.
-
E.
affectsPlantPart
Indicates that one entity produces an influence, change, or impact on a specific part of a plant.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:32 p.m.