Triple
T28694435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phytophthora capsici |
E729374
|
entity |
| Predicate | survivalStructure |
P21744
|
FINISHED |
| Object | oospores in soil |
—
|
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: oospores in soil | Statement: [Phytophthora capsici, survivalStructure, oospores in soil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivalStructure Context triple: [Phytophthora capsici, survivalStructure, oospores in soil]
-
A.
survivingStructure
Indicates that a structure continues to exist or remain intact after a potentially destructive event or over a significant period of time.
-
B.
survivesIn
chosen
Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
-
C.
survivalTheme
Indicates that the relationship or situation centers on the struggle to stay alive or endure extreme hardship.
-
D.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
E.
survivorsBuilt
Indicates that the entities identified as survivors constructed, created, or established the associated object or structure.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f656ad826c8190a0ac00b608d40467 |
completed | May 2, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:38 a.m.