Triple

T10104813
Position Surface form Disambiguated ID Type / Status
Subject IBM API Connect E216289 entity
Predicate supportsStandard P1587 FINISHED
Object GraphQL E208081 NE 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: GraphQL | Statement: [IBM API Connect, supportsStandard, GraphQL]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: GraphQL
Context triple: [IBM API Connect, supportsStandard, GraphQL]
  • A. GraphQL chosen
    GraphQL is a query language and runtime for APIs that enables clients to request exactly the data they need from servers in a flexible, efficient way.
  • B. GraphQL Foundation
    The GraphQL Foundation is an open-source, vendor-neutral organization under the Linux Foundation that stewards the development, ecosystem, and community of the GraphQL query language.
  • C. GraphQL.js
    GraphQL.js is the official JavaScript reference implementation of the GraphQL query language, providing tools to build GraphQL schemas and execute queries in Node.js and browser environments.
  • D. graphql-java
    graphql-java is a popular Java implementation of the GraphQL specification used to build GraphQL APIs on the JVM.
  • E. Apollo Client
    Apollo Client is a popular open-source JavaScript state management and data-fetching library designed to work seamlessly with GraphQL APIs on the client side.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca83d039f08190b9d10363221c69fb completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cdd09dde888190bb550a3cd0b204fe completed April 2, 2026, 2:12 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2cbf9ffb88190a87833d6fe080950 completed April 5, 2026, 8:54 p.m.
Created at: March 30, 2026, 9:03 p.m.