Triple
T18800797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AWS CDK |
E459748
|
entity |
| Predicate | supportsService |
P203
|
FINISHED |
| Object | AWS App Runner |
—
|
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: AWS App Runner | Statement: [AWS CDK, supportsService, AWS App Runner]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AWS App Runner Context triple: [AWS CDK, supportsService, AWS App Runner]
-
A.
AWS App Runner
chosen
AWS App Runner is a fully managed service from Amazon Web Services that makes it easy to build, deploy, and run containerized web applications and APIs at scale without managing infrastructure.
-
B.
Cloud Run
Cloud Run is a fully managed serverless compute platform from Google Cloud that runs containerized applications and APIs that scale automatically on demand.
-
C.
AWS Fargate
AWS Fargate is a serverless compute engine for containers that lets users run Docker-based applications on AWS without managing underlying servers or clusters.
-
D.
AWS Lambda
AWS Lambda is a serverless compute service that lets developers run code in response to events without provisioning or managing servers.
-
E.
Azure App Service
Azure App Service is a fully managed platform-as-a-service (PaaS) offering from Microsoft Azure for building, deploying, and scaling web apps and APIs.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a02332d88190b68feea7f2f86d06 |
completed | April 20, 2026, 3:40 a.m. |
Created at: April 10, 2026, 11:53 a.m.