Triple

T17499621
Position Surface form Disambiguated ID Type / Status
Subject Amazon EventBridge E426156 entity
Predicate integratesWith P1075 FINISHED
Object AWS Backup 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 Backup | Statement: [Amazon EventBridge, integratesWith, AWS Backup]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: AWS Backup
Context triple: [Amazon EventBridge, integratesWith, AWS Backup]
  • A. AWS Backup chosen
    AWS Backup is a fully managed cloud backup service that centralizes and automates data protection across AWS services and on-premises environments.
  • B. Azure Backup
    Azure Backup is a cloud-based backup and recovery service that protects on-premises and Azure workloads by securely storing data in Microsoft’s Azure platform.
  • C. Amazon Data Lifecycle Manager
    Amazon Data Lifecycle Manager is an AWS service that automates the creation, retention, and deletion of EBS snapshots and EBS-backed AMIs according to user-defined lifecycle policies.
  • D. AWS Storage Gateway
    AWS Storage Gateway is a hybrid cloud storage service that connects on-premises environments to AWS cloud storage for backup, archiving, and disaster recovery.
  • E. AWS
    AWS is a train protection and warning system used on railways to alert drivers to signal aspects and speed restrictions, enhancing operational safety.
  • 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_69d889dd9164819087b1dc3c9240c870 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e452112ff0819089c2951baba90102 completed April 19, 2026, 3:54 a.m.
Created at: April 10, 2026, 5:48 a.m.