Triple
T17561882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DynamoDB Streams |
E427710
|
entity |
| Predicate | predicateType |
P5567
|
FINISHED |
| Object | optional feature |
—
|
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: optional feature | Statement: [DynamoDB Streams, predicateType, optional feature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predicateType Context triple: [DynamoDB Streams, predicateType, optional feature]
-
A.
predicateOf
Indicates that one entity functions as a predicate or predicative expression that attributes a property, relation, or condition to another entity.
-
B.
predicate
Indicates that a specified relationship or action holds between given entities, without specifying its particular nature.
-
C.
parentType
Indicates that one entity serves as the direct parent or higher-level type from which another entity is derived or classified.
-
D.
termType
chosen
Indicates the classification or category of a term within a system, specifying what kind of term it is (e.g., type, role, or function) in relation to others.
-
E.
semanticType
Indicates that something belongs to or is categorized under a particular semantic class or type based on its meaning.
- 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.