Triple
T4279930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amazon DynamoDB |
E97122
|
entity |
| Predicate | offersSLA |
P9404
|
FINISHED |
| Object | high availability |
—
|
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: high availability | Statement: [Amazon DynamoDB, offersSLA, high availability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersSLA Context triple: [Amazon DynamoDB, offersSLA, high availability]
-
A.
offersServiceTo
Indicates that one entity provides or makes a service available for the benefit or use of another entity.
-
B.
offersFeature
chosen
Indicates that one entity provides or makes available a particular feature or capability to another entity.
-
C.
offersGrade
Indicates that one entity assigns or provides an academic grade or evaluation to another entity.
-
D.
offersSolution
Indicates that one entity provides or proposes a remedy, answer, or way to resolve a problem or need experienced by another entity.
-
E.
offersServiceType
Indicates that one entity provides or makes available a specific type or category of service to another entity or the public.
- 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_69b34544be3c819084d1ab82d29f90c5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b350367da48190b735deef9b5d2d2e |
completed | March 12, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69b347fc4c0c8190a7fcd814e27308a5 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.