Triple
T12322831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AWS CodeDeploy |
E293764
|
entity |
| Predicate | supportsDeploymentType |
P85293
|
FINISHED |
| Object | in-place deployment |
—
|
LITERAL FINISHED |
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: in-place deployment | Statement: [AWS CodeDeploy, supportsDeploymentType, in-place deployment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDeploymentType Context triple: [AWS CodeDeploy, supportsDeploymentType, in-place deployment]
-
A.
deploymentType
Indicates the manner or configuration in which a system, application, or component is deployed or made operational.
-
B.
typeOfDeployment
Indicates the specific manner or configuration in which something (such as a system, application, or resource) is deployed or made operational.
-
C.
canDeployAs
chosen
Indicates that one entity is capable of being deployed or instantiated in the role, form, or environment represented by another entity.
-
D.
supportsWorkloadType
Indicates that one entity is capable of handling, operating with, or being compatible with a specified type of workload.
-
E.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
- F. None of above.
Provenance (3 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec5be788190b82d2edc6a0f1095 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.