Triple

T30099258
Position Surface form Disambiguated ID Type / Status
Subject Philornis downsi E764946 entity
Predicate vectorStatus P168449 FINISHED
Object not known as a human disease vector 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: not known as a human disease vector | Statement: [Philornis downsi, vectorStatus, not known as a human disease vector]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: vectorStatus
Context triple: [Philornis downsi, vectorStatus, not known as a human disease vector]
  • A. binaryStatus
    Indicates that something has one of two possible states or conditions, typically representing a simple on/off or true/false status.
  • B. vowStatus
    Indicates the current state or condition of a commitment or promise made between entities, such as whether it is active, fulfilled, or broken.
  • C. structureStatus
    Indicates the current condition or state of completion of a structure in relation to its intended design or function.
  • D. coordinateStatus
    Indicates that one entity’s status is aligned, synchronized, or made consistent with another entity’s status or with a shared reference state.
  • E. collectiveStatus
    Indicates the overall state or condition shared by a group of entities considered together as a collective.
  • F. None of above. chosen

Provenance (4 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_69f22474e4288190b5f895fe3974aa92 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f67d93f15c8190973da1ff08641d9c completed May 2, 2026, 10:41 p.m.
PD Predicate disambiguation batch_69f673c664f08190b4d66cdc305e10db completed May 2, 2026, 9:59 p.m.
PDg Predicate description generation batch_69f6749f205c81909d1aacf462912eee completed May 2, 2026, 10:03 p.m.
Created at: April 29, 2026, 7:08 p.m.