Triple

T10292316
Position Surface form Disambiguated ID Type / Status
Subject human adenovirus serotype 26 E241391 entity
Predicate boostCompatibility P92937 FINISHED
Object can be combined with other vector platforms 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: can be combined with other vector platforms | Statement: [human adenovirus serotype 26, boostCompatibility, can be combined with other vector platforms]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: boostCompatibility
Context triple: [human adenovirus serotype 26, boostCompatibility, can be combined with other vector platforms]
  • A. backwardCompatibility
    Indicates that one entity remains functional or compatible when used with an earlier version or older form of another entity.
  • B. backwardCompatibleWith
    Indicates that one entity can correctly interpret, use, or function with data, interfaces, or behavior designed for an earlier version of another entity.
  • C. requiresCompatibilityWith
    Indicates that one entity can only function correctly or be used if it is compatible with another specified entity.
  • D. checksCompatibilityWith
    Indicates that one entity evaluates whether it is compatible or can function harmoniously with another entity.
  • E. compatibilityGoal
    Indicates that one entity has an objective or intended outcome related to being compatible or achieving compatibility with another entity.
  • 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_69d381aaafc08190af475ef58dc16aba completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d2d35f048190a215493acdf1f718 completed April 7, 2026, 9:48 a.m.
PD Predicate disambiguation batch_69d4d1f35e548190be3b4d92d65d2d20 completed April 7, 2026, 9:44 a.m.
PDg Predicate description generation batch_69d4d29d7cf08190acd70cee634c5cdb completed April 7, 2026, 9:47 a.m.
Created at: April 6, 2026, 11:42 a.m.