Triple
T17561886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DynamoDB Streams |
E427710
|
entity |
| Predicate | streamRecordContains |
P122753
|
FINISHED |
| Object | event name |
—
|
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: event name | Statement: [DynamoDB Streams, streamRecordContains, event name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streamRecordContains Context triple: [DynamoDB Streams, streamRecordContains, event name]
-
A.
containsRecord
chosen
Indicates that one entity holds, includes, or stores a particular record within it.
-
B.
streamingRecord
Indicates that an entity maintains a record or log of streaming activity or streamed content associated with another entity.
-
C.
hasRecordingWith
Indicates that one entity is associated with or includes a particular recording as part of its content or representation.
-
D.
streams
Indicates that one entity continuously transmits or delivers data, media, or content in real time to another entity.
-
E.
currentContains
Indicates that one entity presently includes, encloses, or has another entity within its bounds or scope.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e456274c888190ac80402e391674dd |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.