Triple
T12324305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amazon EBS |
E293788
|
entity |
| Predicate | volumeAttachmentScope |
P74565
|
FINISHED |
| Object | single Availability Zone |
—
|
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: single Availability Zone | Statement: [Amazon EBS, volumeAttachmentScope, single Availability Zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: volumeAttachmentScope Context triple: [Amazon EBS, volumeAttachmentScope, single Availability Zone]
-
A.
volumeLimitationBasis
Indicates the rule, criterion, or reference measure used as the basis for determining a limitation on volume.
-
B.
volumeIdentifierLengthLimit
Indicates the maximum allowed length for a volume’s identifier within a given system or context.
-
C.
availabilityScope
chosen
Indicates the extent or context within which something is available, accessible, or applicable.
-
D.
supportsBlockStorage
Indicates that one entity provides or is compatible with block-level storage capabilities for another entity.
-
E.
volumeNameLengthLimit
Indicates the maximum allowed length for a volume’s name in this context.
- 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.