Triple
T17519450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenAPI Specification |
E426647
|
entity |
| Predicate | namespace |
P23103
|
FINISHED |
| Object | openapi |
—
|
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: openapi | Statement: [OpenAPI Specification, namespace, openapi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: openapi Context triple: [OpenAPI Specification, namespace, openapi]
-
A.
OpenAPI
chosen
OpenAPI is a widely adopted, language-agnostic specification for describing and documenting RESTful APIs in a standardized, machine-readable format.
-
B.
Swagger
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.
-
C.
OpenAPI Initiative
The OpenAPI Initiative is an open governance consortium that stewards the OpenAPI Specification, a widely adopted standard for describing and documenting RESTful APIs.
-
D.
SwaggerHub
SwaggerHub is a collaborative, cloud-based platform for designing, documenting, and managing APIs using the OpenAPI (Swagger) specification.
-
E.
OpenAPI Generator
OpenAPI Generator is a tool that automatically generates client libraries, server stubs, API documentation, and configuration from OpenAPI specifications to streamline API development.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d18c1c81908bb843bbddb44ca1 |
completed | April 19, 2026, 3:58 a.m. |
Created at: April 10, 2026, 5:49 a.m.