Triple
T28610869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QMP |
E724164
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | JSON-based protocol |
C993
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: JSON-based protocol Context triple: [QMP, instanceOf, JSON-based protocol]
-
A.
JSON specification
A JSON specification defines the structured format, syntax rules, and data types for representing and exchanging data using JavaScript Object Notation.
-
B.
HTTP-based API
An HTTP-based API is an interface that enables communication between software systems over the web using standard HTTP methods (such as GET, POST, PUT, and DELETE) to request and manipulate resources.
-
C.
web protocol
A web protocol is a standardized set of rules and formats that govern how data is requested, transmitted, and received between clients and servers over the World Wide Web.
-
D.
blockchain-based protocol
A blockchain-based protocol is a decentralized set of rules and procedures encoded on a distributed ledger that governs how participants validate, record, and agree on transactions or data without relying on a central authority.
-
E.
communication protocol
chosen
A communication protocol is a defined set of rules and formats that enable reliable, structured exchange of data between two or more communicating entities in a networked system.
- F. None of above.
Provenance (1 batch)
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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:30 a.m.