Triple
T12322671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AWS Backup |
E293761
|
entity |
| Predicate | supportsHybridEnvironments |
P11908
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [AWS Backup, supportsHybridEnvironments, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHybridEnvironments Context triple: [AWS Backup, supportsHybridEnvironments, true]
-
A.
supportsBigLittleHybrid
Indicates that an entity is compatible with or enables operation using a big.LITTLE-style heterogeneous core or component configuration.
-
B.
supportsEnvironment
chosen
Indicates that one entity provides the necessary conditions, compatibility, or resources for another entity to operate or exist within a particular environment.
-
C.
offersHybridVariantIn
Indicates that an entity provides a hybrid (e.g., partially electric or mixed-mode) version of a product or service within a specified context, such as a market, region, or model line.
-
D.
supportsEnvironmentMapping
Indicates that one entity provides or enables environment mapping functionality for another entity or context.
-
E.
usedHybridSittings
Indicates that an entity has conducted or participated in sessions or meetings that combined both in-person and remote (virtual) attendance formats.
- 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.