Triple

T722386
Position Surface form Disambiguated ID Type / Status
Subject PT-91 Twardy E14645 entity
Predicate hasAutoloader P18624 FINISHED
Object yes 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: yes | Statement: [PT-91 Twardy, hasAutoloader, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAutoloader
Context triple: [PT-91 Twardy, hasAutoloader, yes]
  • A. hasModuleConstruct
    Indicates that an entity includes, defines, or is composed of a specific module as one of its structural or functional components.
  • B. hasDynamicalClass
    Indicates that an entity belongs to a specific category defined by its dynamical or motion-related behavior (e.g., orbital or kinematic characteristics).
  • C. hasIndex
    Indicates that one entity serves as an index or positional reference for another entity within an ordered collection or structure.
  • D. hasAsset
    Indicates that one entity possesses, owns, or controls another entity as an asset.
  • E. hasServiceClass
    Indicates that an entity is associated with, or categorized under, a particular class or type of service.
  • 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_69a4934c753c81909b309027e48b9b3a completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a591124c8190842e7ef18b064198 completed March 1, 2026, 8:46 p.m.
PD Predicate disambiguation batch_69a4a4f700cc81908c6de3eedf68433c completed March 1, 2026, 8:43 p.m.
PDg Predicate description generation batch_69a4a55a26e081908134ee93faaf7c40 completed March 1, 2026, 8:45 p.m.
Created at: March 1, 2026, 7:37 p.m.