Triple
T17598632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anypoint Studio |
E428636
|
entity |
| Predicate | supports |
P516
|
FINISHED |
| Object | RAML |
—
|
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: RAML | Statement: [Anypoint Studio, supports, RAML]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RAML Context triple: [Anypoint Studio, supports, RAML]
-
A.
RAML
chosen
RAML (RESTful API Modeling Language) is a human-readable language used to design, document, and model RESTful APIs in a structured, reusable way.
-
B.
WADL
WADL is the ICAO airport code for Lombok International Airport in Indonesia.
-
C.
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.
-
D.
OpenAPI
OpenAPI is a widely adopted, language-agnostic specification for describing and documenting RESTful APIs in a standardized, machine-readable format.
-
E.
Remote API (RAPI)
Remote API (RAPI) is a Microsoft technology that allows desktop applications to remotely access and control resources on Windows Mobile and Windows CE devices programmatically.
- 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.