Triple
T32413985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | API Apps |
E828294
|
entity |
| Predicate | supportsDeploymentSource |
—
|
GENERATED |
| Object | GitHub |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDeploymentSource Context triple: [API Apps, supportsDeploymentSource, GitHub]
-
A.
deploymentSource
chosen
Indicates the origin or mechanism from which something is deployed, such as the system, process, or source responsible for initiating the deployment.
-
B.
canDeployWith
Indicates that one entity is compatible or allowed to be deployed together with another entity in the same environment or configuration.
-
C.
canDeployAs
Indicates that one entity is capable of being deployed or instantiated in the role, form, or environment represented by another entity.
-
D.
canDeploy
Indicates that one entity has the permission or capability to deploy another entity (such as software, resources, or configurations) into a target environment.
-
E.
supportsInstallation
Indicates that one entity is capable of enabling, handling, or being compatible with the installation of another entity.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:53 a.m.