Triple
T17598446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swagger |
E428632
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | API Blueprint |
—
|
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: API Blueprint | Statement: [Swagger, relatedTo, API Blueprint]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: API Blueprint Context triple: [Swagger, relatedTo, API Blueprint]
-
A.
API Blueprint
chosen
API Blueprint is a high-level, markdown-based language and format for designing, documenting, and testing web APIs in a human- and machine-readable way.
-
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
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 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.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c474e5481909d2736241b592dab |
completed | April 19, 2026, 5:46 a.m. |
Created at: April 10, 2026, 5:51 a.m.