Triple

T16150612
Position Surface form Disambiguated ID Type / Status
Subject Solenopsis invicta virus 1 E391899 entity
Predicate naturalHostRange P2901 FINISHED
Object Solenopsis invicta colonies 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: Solenopsis invicta colonies | Statement: [Solenopsis invicta virus 1, naturalHostRange, Solenopsis invicta colonies]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: naturalHostRange
Context triple: [Solenopsis invicta virus 1, naturalHostRange, Solenopsis invicta colonies]
  • A. hostSpecies
    Indicates the species that serves as the host for another organism, agent, or entity.
  • B. hostRange chosen
    Indicates the range or set of different hosts that an organism, agent, or system can successfully inhabit, infect, or interact with.
  • C. targetOrganism
    Indicates that an action, process, or effect is directed toward or intended to impact a particular organism.
  • D. reservoirHost
    Indicates that one entity serves as a natural long-term host in which a pathogen is maintained and from which it can be transmitted to other susceptible entities.
  • E. mayHost
    Indicates that an entity is permitted or able to serve as the location or organizer for another entity or event.
  • 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_69d87f1c65e48190aa2b4c472e9bafc4 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e21d9724808190a8332987583a345a completed April 17, 2026, 11:46 a.m.
PD Predicate disambiguation batch_69e1828abb608190a99d86bce1d77de2 completed April 17, 2026, 12:44 a.m.
Created at: April 10, 2026, 5:01 a.m.