Triple
T50259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch elm disease |
E987
|
entity |
| Predicate | preventionStrategy |
P1040
|
FINISHED |
| Object | planting resistant elm cultivars |
—
|
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: planting resistant elm cultivars | Statement: [Dutch elm disease, preventionStrategy, planting resistant elm cultivars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preventionStrategy Context triple: [Dutch elm disease, preventionStrategy, planting resistant elm cultivars]
-
A.
protects
chosen
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
-
B.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
C.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
D.
securityProgram
Indicates that an entity is associated with, participates in, or is governed by a security program, such as a set of policies, controls, or initiatives related to safety or protection.
-
E.
protectedIn
Indicates that one entity is safeguarded, preserved, or kept safe within the context, environment, or jurisdiction of another entity.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24ba7016481909d595402712db6e2 |
completed | Feb. 28, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69a24ac23f04819080cef9365ed990d4 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.