Triple
T193157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DOM |
E3762
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Application programming interface |
C227
|
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: Application programming interface Context triple: [DOM, instanceOf, Application programming interface]
-
A.
application-layer protocol
An application-layer protocol defines the rules and formats for how software applications communicate and exchange data over a network, sitting at the top of the protocol stack to support end-user services.
-
B.
software
chosen
Software is a collection of programs, data, and instructions that tell a computer or digital device how to perform specific tasks or functions.
-
C.
communication protocol suite
A communication protocol suite is a coordinated set of network protocols that work together across different layers to enable reliable data exchange between devices in a communication system.
-
D.
computer hardware interface
A computer hardware interface is the physical and logical connection standard that enables communication and data exchange between a computer’s internal components or external devices and the system.
-
E.
internet protocol suite
The internet protocol suite is a conceptual framework of layered communication protocols (including TCP/IP) that defines how data is formatted, addressed, transmitted, routed, and received across interconnected computer networks.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.