Triple

T27730339
Position Surface form Disambiguated ID Type / Status
Subject RPC over HTTP E697414 entity
Predicate supportedInProduct P48616 FINISHED
Object Microsoft Exchange Server 2003 NE NERFINISHED

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: Microsoft Exchange Server 2003 | Statement: [RPC over HTTP, supportedInProduct, Microsoft Exchange Server 2003]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportedInProduct
Context triple: [RPC over HTTP, supportedInProduct, Microsoft Exchange Server 2003]
  • A. supportsProduct
    Indicates that one entity provides assistance, compatibility, or necessary resources for the operation, use, or maintenance of a specified product.
  • 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. supportedAs
    Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
  • D. isSupportedBy
    Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
  • E. isSupportedFor
    Indicates that one entity provides compatibility, assistance, or backing necessary for another entity’s proper use or operation.
  • 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_69ef590c3e288190ad54d2465af8ca4e completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69ffb1218cb08190a814c7f0833501a7 completed May 9, 2026, 10:11 p.m.
PD Predicate disambiguation batch_69ffb083d6988190b2757e0cfd629b75 completed May 9, 2026, 10:09 p.m.
Created at: April 27, 2026, 3:11 p.m.