Triple
T23154310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MicroProfile |
E578399
|
entity |
| Predicate | includesAPI |
P126488
|
FINISHED |
| Object | MicroProfile 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: MicroProfile OpenAPI | Statement: [MicroProfile, includesAPI, MicroProfile OpenAPI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MicroProfile OpenAPI Context triple: [MicroProfile, includesAPI, MicroProfile OpenAPI]
-
A.
MicroProfile
chosen
MicroProfile is an open-source specification and set of APIs designed to optimize Enterprise Java for building and running cloud-native, microservices-based applications.
-
B.
OpenAPI
OpenAPI is a widely adopted, language-agnostic specification for describing and documenting RESTful APIs in a standardized, machine-readable format.
-
C.
OpenAPI ecosystem
The OpenAPI ecosystem is a community and set of tools, standards, and practices built around the OpenAPI Specification to design, document, and integrate RESTful APIs.
-
D.
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.
-
E.
AsyncAPI
AsyncAPI is an open standard and specification for defining and documenting asynchronous, event-driven APIs and messaging systems.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18efbe9a08190bcb6e822b8eab544 |
completed | April 29, 2026, 4:54 a.m. |
Created at: April 17, 2026, 4:01 p.m.