Triple

T470297
Position Surface form Disambiguated ID Type / Status
Subject Ulmus laevis E8539 entity
Predicate lessSusceptibleTo P583 FINISHED
Object Dutch elm disease than Ulmus minor 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: Dutch elm disease than Ulmus minor | Statement: [Ulmus laevis, lessSusceptibleTo, Dutch elm disease than Ulmus minor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lessSusceptibleTo
Context triple: [Ulmus laevis, lessSusceptibleTo, Dutch elm disease than Ulmus minor]
  • A. susceptibleTo chosen
    Indicates that one entity is vulnerable or likely to be affected, harmed, or influenced by another entity or factor.
  • B. isSubjectTo
    Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
  • C. mayReportTo
    Indicates that one entity is permitted or allowed to have a reporting relationship to another entity, such as an employee being allowed to report to a particular manager.
  • D. isDifficultToAccessBecauseOf
    Indicates that something is hard to reach, obtain, or use due to a specified obstacle, condition, or circumstance.
  • E. mayResultIn
    Indicates that one entity has the potential to cause, lead to, or bring about another entity or outcome, without guaranteeing that it will occur.
  • 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_69a2e7f3aeb48190a19453e3a043f486 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2efef8b788190857ebf66df562d59 completed Feb. 28, 2026, 1:38 p.m.
PD Predicate disambiguation batch_69a2edecefb081908331ef8b9edf6636 completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.