Triple

T28617047
Position Surface form Disambiguated ID Type / Status
Subject Winsock 1.1 API E724294 entity
Predicate limitedFeatureComparedTo P83869 FINISHED
Object Winsock 2.0 API 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: Winsock 2.0 API | Statement: [Winsock 1.1 API, limitedFeatureComparedTo, Winsock 2.0 API]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: limitedFeatureComparedTo
Context triple: [Winsock 1.1 API, limitedFeatureComparedTo, Winsock 2.0 API]
  • A. lessFeatureRichThan chosen
    Indicates that one entity has fewer or less advanced features or capabilities than another entity.
  • B. lacksAdvancedBusinessFeaturesComparedTo
    Indicates that one entity does not possess the same level or range of advanced business-related features as the entity it is being compared to.
  • C. offersFewerBusinessFocusedFeaturesThan
    Indicates that one entity provides a smaller or less comprehensive set of business-oriented features compared to another entity.
  • D. limitedSystemType
    Indicates that the system is restricted to a specific subset or category of system types, rather than allowing all possible types.
  • E. reasonForLimitedAdoption
    Indicates the factor or explanation that accounts for why something has not been widely or fully adopted.
  • 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_69f01d816d7c8190a1fe27e3434041dc completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69f652a492108190b885b955ce147d3c completed May 2, 2026, 7:38 p.m.
PD Predicate disambiguation batch_69f651aad92c8190b874b3b5f9f64434 completed May 2, 2026, 7:34 p.m.
Created at: April 28, 2026, 4:32 a.m.