Triple

T23689869
Position Surface form Disambiguated ID Type / Status
Subject Spilocaea pomi E585265 entity
Predicate requiresForInfection P69969 FINISHED
Object leaf wetness 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: leaf wetness | Statement: [Spilocaea pomi, requiresForInfection, leaf wetness]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresForInfection
Context triple: [Spilocaea pomi, requiresForInfection, leaf wetness]
  • A. infectionRequires chosen
    Indicates that the occurrence or establishment of an infection depends on the presence or fulfillment of a specified condition, factor, or prerequisite.
  • B. requiresForFeature
    Indicates that one entity must be present, implemented, or satisfied in order for a particular feature of another entity to be available or function correctly.
  • C. requiresDetectionOf
    Indicates that one entity can only occur, be valid, or proceed if another entity has first been detected or identified.
  • D. requiresApplicationOf
    Indicates that performing one entity or process depends on actively applying or using another entity, method, or resource.
  • E. requiresForDefense
    Indicates that one entity must have or obtain another entity as a necessary condition to provide or maintain defense.
  • 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_69e249037ce0819088b149608e98f685 completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1b5c16af08190b2f4d126c60a7e75 completed April 29, 2026, 7:39 a.m.
PD Predicate disambiguation batch_69f155d5265881908e43a9696b6a6d0f completed April 29, 2026, 12:50 a.m.
Created at: April 17, 2026, 6:52 p.m.