Triple

T7893408
Position Surface form Disambiguated ID Type / Status
Subject REST API E183290 entity
Predicate oftenDocumentedWith P38828 FINISHED
Object Swagger E428632 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: Swagger | Statement: [REST API, oftenDocumentedWith, Swagger]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Swagger
Context triple: [REST API, oftenDocumentedWith, Swagger]
  • A. Swagger chosen
    Swagger is an open-source framework and toolset for designing, documenting, and consuming RESTful APIs, which later evolved into and helped define the OpenAPI Specification.
  • B. Swagger UI
    Swagger UI is an open-source tool that automatically generates interactive, web-based user interfaces for exploring and testing RESTful APIs defined with the OpenAPI specification.
  • C. OpenAPI
    OpenAPI is a widely adopted, language-agnostic specification for describing and documenting RESTful APIs in a standardized, machine-readable format.
  • D. SwaggerHub
    SwaggerHub is a collaborative, cloud-based platform for designing, documenting, and managing APIs using the OpenAPI (Swagger) specification.
  • E. Swagger Editor
    Swagger Editor is an open-source, browser-based tool for designing, editing, and validating OpenAPI/Swagger API definitions in YAML or JSON.
  • 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_69ca828c474c8190a254d6499871eaff completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3a008fb88190a039fec40483ab93 completed March 31, 2026, 3:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69cb5ba9c2ac8190b8faf1518390dff4 completed March 31, 2026, 5:29 a.m.
Created at: March 30, 2026, 5 p.m.