Triple

T7857525
Position Surface form Disambiguated ID Type / Status
Subject Microsoft Office RT E182414 entity
Predicate addInSupport P48616 FINISHED
Object no support for traditional COM add-ins 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: no support for traditional COM add-ins | Statement: [Microsoft Office RT, addInSupport, no support for traditional COM add-ins]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: addInSupport
Context triple: [Microsoft Office RT, addInSupport, no support for traditional COM add-ins]
  • A. providesSupportTo
    Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
  • B. supportedIn chosen
    Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
  • C. addedFor
    Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of another entity.
  • D. supportedAs
    Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
  • E. supportedAct
    Indicates that one entity provided assistance, endorsement, or backing for a particular action or activity performed by another entity.
  • 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_69ca82887fd48190975896bf38c4596b completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb1a76f8648190976b488d0d8658ef completed March 31, 2026, 12:51 a.m.
PD Predicate disambiguation batch_69cae925ca388190ae4a01fa76e957e8 completed March 30, 2026, 9:20 p.m.
Created at: March 30, 2026, 4:52 p.m.