Triple

T8574266
Position Surface form Disambiguated ID Type / Status
Subject MS-DOS Executive E203006 entity
Predicate fileAssociationMechanism P83711 FINISHED
Object extension-based associations 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: extension-based associations | Statement: [MS-DOS Executive, fileAssociationMechanism, extension-based associations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fileAssociationMechanism
Context triple: [MS-DOS Executive, fileAssociationMechanism, extension-based associations]
  • A. extensionMechanism
    Indicates that one entity provides a way to extend, customize, or add new functionality or components to another entity.
  • B. fileTypeMasquerade
    Indicates that a file is presented or labeled as one type while actually being of a different underlying type.
  • C. hostAssociation
    Indicates a relationship in which one entity serves as the host or primary supporting environment for another entity.
  • D. fileManagementModel
    Indicates a relationship where a model or system is responsible for organizing, storing, modifying, or otherwise managing files and their associated operations.
  • E. registerFileUsed
    Indicates that a particular register file is utilized or accessed in the given context or operation.
  • 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_69ca8328ebe481909a8c038fa79959b4 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbea947f188190af469babaa73ddf6 completed March 31, 2026, 3:39 p.m.
PD Predicate disambiguation batch_69cbd11856048190a1ce4b83a38f6965 completed March 31, 2026, 1:50 p.m.
PDg Predicate description generation batch_69cbe30e37ac8190b685df36274602b5 completed March 31, 2026, 3:06 p.m.
Created at: March 30, 2026, 6:21 p.m.